Skip to content

Add model prefix validation to PR review workflow#648

Merged
functionstackx merged 1 commit intomainfrom
claude/add-model-prefix-validation
Feb 5, 2026
Merged

Add model prefix validation to PR review workflow#648
functionstackx merged 1 commit intomainfrom
claude/add-model-prefix-validation

Conversation

@Klaud-Cold
Copy link
Copy Markdown
Collaborator

Summary

Adds a validation rule to the Claude PR review workflow to ensure that config keys in master config files only use valid model prefixes (dsr1 or gptoss).

Why this is needed:

  • The frontend only expects dsr1 and gptoss as model prefixes
  • Using invalid prefixes like dsr1-fp8 breaks the frontend and prevents benchmark results from being displayed
  • This validation will catch these issues during PR review before they're merged

Changes:

  • Added new "Model Prefix Validation" section to .github/workflows/claude-pr-review.yml
  • Claude will now flag any config key using an invalid model prefix as a 🔴 BLOCKING issue
  • Error message explains the valid format and why invalid prefixes break the frontend

Related context: See discussion in PR #627 where dsr1-fp8 prefix was identified as breaking the frontend.


🤖 Generated with Claude Code

Add validation rule to ensure config keys only use valid model prefixes
(dsr1 or gptoss). Invalid prefixes like dsr1-fp8 will now trigger a
BLOCKING comment explaining that it breaks the frontend.

Co-authored-by: functionstackx <functionstackx@users.noreply.github.com>
@Klaud-Cold Klaud-Cold requested a review from a team as a code owner February 5, 2026 04:01
@functionstackx functionstackx merged commit 81e134e into main Feb 5, 2026
@functionstackx functionstackx deleted the claude/add-model-prefix-validation branch February 5, 2026 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants