coderabbit-upgrade-migration
Update CodeRabbit configuration for new features, migrate between plans, and adopt new capabilities. Use when CodeRabbit releases new features, upgrading from Free to Pro plan, or updating .coderabbit.yaml schema for new options. Trigger with phrases like "upgrade coderabbit", "coderabbit new features", "update coderabbit config", "coderabbit plan upgrade", "coderabbit changelog".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly identifies the tool (CodeRabbit), lists specific actions, provides explicit 'Use when' guidance, and includes natural trigger phrases. It covers all dimensions effectively with minimal room for improvement. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Update CodeRabbit configuration for new features', 'migrate between plans', and 'adopt new capabilities'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (update configuration, migrate plans, adopt new capabilities) and 'when' (when CodeRabbit releases new features, upgrading plans, updating schema) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'upgrade coderabbit', 'coderabbit new features', 'update coderabbit config', 'coderabbit plan upgrade', 'coderabbit changelog'. Also mentions '.coderabbit.yaml' and 'Free to Pro plan' as additional natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific tool (CodeRabbit) with specific use cases (plan migration, config updates, new feature adoption). The mention of '.coderabbit.yaml' and specific plan names makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows and validation steps for CodeRabbit configuration upgrades. Its main weakness is length — the extensive inline YAML examples and Pro plan feature descriptions make it verbose for a SKILL.md that could delegate detailed configs to reference files. The error handling table and migration checklist are strong additions.
Suggestions
Move the full YAML configuration examples (Steps 3-4) into a separate reference file like CODERABBIT_CONFIG_REFERENCE.md and link to it from the main skill
Remove the 'What you gain with Pro' bullet list in Step 2 — this is marketing information Claude doesn't need to execute the upgrade steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity (e.g., explaining what you gain with Pro in detail, the overview paragraph explaining what CodeRabbit is). The YAML examples are thorough but include inline comments that explain obvious things. Some sections like the upgrade path table add moderate value but could be tighter. | 2 / 3 |
Actionability | The skill provides fully concrete, copy-paste ready YAML configurations, bash validation scripts, specific PR comment commands (@coderabbitai configuration, @coderabbitai run fix-imports), and exact dashboard navigation paths. Every step has executable guidance. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from checking current config through validation. Step 6 provides an explicit validation script, Step 7 provides a migration checklist with verification checkpoints (validate YAML, verify on test PR, test on non-critical PR first). The feedback loop of validate -> fix -> re-verify is present. | 3 / 3 |
Progressive Disclosure | The skill is quite long with all content inline in a single file. The YAML configuration examples are extensive and could be split into separate reference files. The Resources section at the end provides external links, but the main body could benefit from splitting the full config example and recipes into referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.