Replace retired Claude model ids in commands, skills and converter docs - #274
Replace retired Claude model ids in commands, skills and converter docs#274kasparovabi wants to merge 2 commits into
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
codeant-ai
Bot
added
the
size:S
🤖 My Senior Dev — Analysis Complete👤 For @kasparovabi📁 Expert in View your contributor analytics → 📊 10 files reviewed • 1 need attention ✅ No high-risk areas found 🚀 Open Interactive Review →The full interface unlocks features not available in GitHub:
💬 Chat here: 📖 View all 12 personas & slash commandsYou can interact with me by mentioning In PR comments or on any line of code:
Slash commands:
AI Personas (mention to get their perspective):
For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
3 issues found across 10 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/converters/docs/opencode.md">
<violation number="1" location="packages/converters/docs/opencode.md:66">
P3: The migration is incomplete within the same files this PR touches. The model-field example was updated on this line, but the field-description examples in opencode.md (line 38) and both opencode schemas (opencode.schema.json:26, opencode-slash-command.schema.json:28) still reference the retired `anthropic/claude-sonnet-4-20250514` ID. Since the PR's goal is to remove retired IDs (the retained-files note doesn't cover these references), update those descriptions to `anthropic/claude-sonnet-4-6` too so docs and schema examples stay consistent.</violation>
</file>
<file name=".claude/skills/slash-command-builder/EXAMPLES.md">
<violation number="1" location=".claude/skills/slash-command-builder/EXAMPLES.md:68">
P3: The 'Available Models' reference list (lines 149-151) in this touched file still shows the retired IDs (claude-3-5-haiku-20241022, claude-3-5-sonnet-20241022, claude-opus-4-20250514) even though the examples right below were updated. This leaves the skill instructing readers to use retired models and the checker this PR supports would still flag this file. Update the list to match the new IDs.</violation>
<violation number="2" location=".claude/skills/slash-command-builder/EXAMPLES.md:68">
P3: The 'When to use different models' list (lines 239-241) in this touched skill still advertises the retired IDs while the example just above was updated to claude-haiku-4-5-20251001. Readers following this section would copy retired model IDs; update it to the current tier equivalents for consistency with the PR goal.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| description: Expert code reviewer focused on best practices and security | ||
| mode: subagent | ||
| model: anthropic/claude-sonnet-4-20250514 | ||
| model: anthropic/claude-sonnet-4-6 |
There was a problem hiding this comment.
P3: The migration is incomplete within the same files this PR touches. The model-field example was updated on this line, but the field-description examples in opencode.md (line 38) and both opencode schemas (opencode.schema.json:26, opencode-slash-command.schema.json:28) still reference the retired anthropic/claude-sonnet-4-20250514 ID. Since the PR's goal is to remove retired IDs (the retained-files note doesn't cover these references), update those descriptions to anthropic/claude-sonnet-4-6 too so docs and schema examples stay consistent.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/converters/docs/opencode.md, line 66:
<comment>The migration is incomplete within the same files this PR touches. The model-field example was updated on this line, but the field-description examples in opencode.md (line 38) and both opencode schemas (opencode.schema.json:26, opencode-slash-command.schema.json:28) still reference the retired `anthropic/claude-sonnet-4-20250514` ID. Since the PR's goal is to remove retired IDs (the retained-files note doesn't cover these references), update those descriptions to `anthropic/claude-sonnet-4-6` too so docs and schema examples stay consistent.</comment>
<file context>
@@ -63,7 +63,7 @@ Note: Any additional fields not listed above will be passed to the model provide
description: Expert code reviewer focused on best practices and security
mode: subagent
-model: anthropic/claude-sonnet-4-20250514
+model: anthropic/claude-sonnet-4-6
temperature: 0.1
tools:
</file context>
| --- | ||
| description: Analyze code quality in current file | ||
| model: claude-3-5-haiku-20241022 | ||
| model: claude-haiku-4-5-20251001 |
There was a problem hiding this comment.
P3: The 'When to use different models' list (lines 239-241) in this touched skill still advertises the retired IDs while the example just above was updated to claude-haiku-4-5-20251001. Readers following this section would copy retired model IDs; update it to the current tier equivalents for consistency with the PR goal.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .claude/skills/slash-command-builder/EXAMPLES.md, line 68:
<comment>The 'When to use different models' list (lines 239-241) in this touched skill still advertises the retired IDs while the example just above was updated to claude-haiku-4-5-20251001. Readers following this section would copy retired model IDs; update it to the current tier equivalents for consistency with the PR goal.</comment>
<file context>
@@ -65,7 +65,7 @@ Provide specific file:line references for all issues found.
---
description: Analyze code quality in current file
-model: claude-3-5-haiku-20241022
+model: claude-haiku-4-5-20251001
---
</file context>
| --- | ||
| description: Analyze code quality in current file | ||
| model: claude-3-5-haiku-20241022 | ||
| model: claude-haiku-4-5-20251001 |
There was a problem hiding this comment.
P3: The 'Available Models' reference list (lines 149-151) in this touched file still shows the retired IDs (claude-3-5-haiku-20241022, claude-3-5-sonnet-20241022, claude-opus-4-20250514) even though the examples right below were updated. This leaves the skill instructing readers to use retired models and the checker this PR supports would still flag this file. Update the list to match the new IDs.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .claude/skills/slash-command-builder/EXAMPLES.md, line 68:
<comment>The 'Available Models' reference list (lines 149-151) in this touched file still shows the retired IDs (claude-3-5-haiku-20241022, claude-3-5-sonnet-20241022, claude-opus-4-20250514) even though the examples right below were updated. This leaves the skill instructing readers to use retired models and the checker this PR supports would still flag this file. Update the list to match the new IDs.</comment>
<file context>
@@ -65,7 +65,7 @@ Provide specific file:line references for all issues found.
---
description: Analyze code quality in current file
-model: claude-3-5-haiku-20241022
+model: claude-haiku-4-5-20251001
---
</file context>
The first commit only changed the `model:` example values, which left several files internally inconsistent: the "Available Models" list in FRONTMATTER.md and the "When to use different models" list in SKILL.md still documented the retired IDs directly above/below the updated examples, and the `model` field descriptions in both opencode schemas, opencode.md and kiro-agents.md still cited the retired IDs as examples. Readers of those sections would have copied retired IDs, and any checker scanning for them would still flag these files. Same mapping as the first commit, applied consistently.
1 participant
User description
Four Claude model ids in this repo passed their retirement dates.
claude-3-5-haiku-20241022andclaude-3-5-sonnet-20241022went out on 28 October 2025,claude-sonnet-4-20250514andclaude-opus-4-20250514later. All four are on the model deprecations page. The one that actually runs is.claude/commands/karen/quick-score.md, where the frontmatter names a model the API no longer serves. The rest are examples people copy.I replaced each id with the current model in the same tier, so a command written for Haiku still gets Haiku.
.claude/commands/karen/quick-score.mdclaude-3-5-haiku-20241022claude-haiku-4-5-20251001.claude/skills/slash-command-builder/SKILL.mdclaude-sonnet-4-6,claude-haiku-4-5-20251001.claude/skills/slash-command-builder/FRONTMATTER.mdclaude-haiku-4-5-20251001,claude-sonnet-4-6,claude-opus-4-8.claude/skills/slash-command-builder/EXAMPLES.mdclaude-3-5-haiku-20241022claude-haiku-4-5-20251001.claude/skills/creating-opencode-agents/SKILL.mdanthropic/claude-sonnet-4-20250514anthropic/claude-sonnet-4-6.cursor/rules/creating-claude-commands.mdclaude-3-5-sonnet-20241022claude-sonnet-4-6packages/converters/docs/kiro-agents.mdclaude-3-5-sonnet-20241022claude-sonnet-4-6packages/converters/docs/opencode.mdanthropic/claude-sonnet-4-20250514anthropic/claude-sonnet-4-6packages/converters/schemas/opencode.schema.jsonanthropic/claude-sonnet-4-20250514anthropic/claude-sonnet-4-6packages/converters/schemas/opencode-slash-command.schema.jsonanthropic/claude-sonnet-4-20250514anthropic/claude-sonnet-4-6Both schema edits sit in the
examplesarray, so validation behaviour is unchanged. I reparsed both files as JSON afterwards. Thetemperaturevalues next to these ids still work on the replacement models and are untouched.Three files carry retired ids that I deliberately left alone.
docs/blog/slash-commands-compared.mdandpackages/webapp/public/blog/extensibility-landscape.mdare published posts. They describe what the ecosystem looked like when you wrote them, and quietly editing that record is your call rather than mine.docs/PLAYGROUND_IMPLEMENTATION_LOG.mdhas one inside a sample API response at line 291. It reads as a record of a response you got, not as guidance, so I left it.I read this diff line by line before opening it, and I am happy to adjust or drop any part of it. What brought me here was a checker I maintain that flags retired Claude model IDs, so I am mentioning that up front rather than leaving you to wonder. I have not run the karen command against the API to reproduce a failure, the claim rests on the published retirement dates. If you would rather handle this your own way, or would rather not get this kind of contribution at all, tell me and I will not send another.
CodeAnt-AI Description
Replace retired Claude model references with current supported models
What Changed
Impact
✅ Fewer command failures from retired model IDs✅ Working copy-and-paste examples✅ Current generated agent configurations💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.