coderabbit-common-errors
Diagnose and fix CodeRabbit common errors and configuration issues. Use when CodeRabbit is not reviewing PRs, posting duplicate comments, ignoring configuration, or behaving unexpectedly. Trigger with phrases like "coderabbit error", "fix coderabbit", "coderabbit not working", "debug coderabbit", "coderabbit broken".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 its niche (CodeRabbit troubleshooting), provides explicit 'Use when' guidance with concrete scenarios, and includes natural trigger phrases. The main area for improvement is the specificity of the concrete actions—it could enumerate more distinct operations beyond the general 'diagnose and fix' framing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CodeRabbit) and some actions ('diagnose and fix', 'not reviewing PRs', 'posting duplicate comments', 'ignoring configuration'), but the core action is fairly general ('diagnose and fix common errors and configuration issues') rather than listing multiple distinct concrete operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix CodeRabbit common errors and configuration issues) and 'when' (explicit 'Use when...' clause with specific scenarios plus a 'Trigger with phrases like...' section providing concrete trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'coderabbit error', 'fix coderabbit', 'coderabbit not working', 'debug coderabbit', 'coderabbit broken'. Also includes natural problem descriptions like 'not reviewing PRs', 'posting duplicate comments', 'ignoring configuration', 'behaving unexpectedly'. | 3 / 3 |
Distinctiveness Conflict Risk | CodeRabbit is a very specific tool, making this skill highly distinctive. The triggers are narrowly scoped to CodeRabbit-specific issues and are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 troubleshooting guide with strong actionability — concrete YAML configs, CLI commands, and verification steps make each fix immediately executable. The symptom-based triage table is an excellent design choice for quick navigation. The main weakness is that the document is somewhat long for a SKILL.md and could benefit from splitting detailed configuration examples into a reference file, and trimming the overview/prerequisites sections.
Suggestions
Move detailed YAML configuration examples (path_filters, path_instructions) into a separate reference file and link from the main skill to improve progressive disclosure.
Trim the Overview paragraph — Claude doesn't need to be told what CodeRabbit is or that most problems are configuration issues; jump straight to the symptom table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and structured sections, but includes some unnecessary framing (e.g., the Overview paragraph explaining what CodeRabbit is, the Prerequisites section stating obvious requirements). The symptom-based lookup table is a nice touch that aids efficiency, but some sections could be tighter. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready YAML configurations, bash commands, and specific PR comment commands for each error scenario. The diagnostic steps are executable (gh CLI commands, Python YAML validation), and the configuration fixes show exact field names and values. | 3 / 3 |
Workflow Clarity | Clear symptom → diagnosis → fix workflow with an explicit verification step (Step 2: Verify Fix) that includes commands to force re-review and check active configuration. The symptom table at the top provides excellent triage, and each error follows a consistent pattern of symptoms, causes, and solutions. | 3 / 3 |
Progressive Disclosure | The content is well-structured with a symptom lookup table and numbered errors, but it's a fairly long monolithic document (~180 lines of content). Some sections like the detailed YAML examples for path_filters or path_instructions could be split into a reference file. The 'Next Steps' reference to coderabbit-debug-bundle is good but is the only external reference. | 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
70e9fa4
- 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.