Configure CodeRabbit CLI for local pre-commit code reviews and fast iteration. Use when setting up local development with CodeRabbit CLI reviews, integrating AI review into your commit workflow, or testing config changes. Trigger with phrases like "coderabbit dev setup", "coderabbit local development", "coderabbit CLI workflow", "coderabbit pre-commit review".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
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 solid skill description that clearly identifies its niche (CodeRabbit CLI local setup) and provides explicit trigger guidance. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., creating config files, setting up git hooks, configuring review rules). The description also uses second person 'your' which is a minor voice issue but doesn't severely impact clarity.
Suggestions
Add more specific concrete actions beyond 'configure' — e.g., 'Creates .coderabbit.yaml config files, sets up pre-commit git hooks, configures review rules' to improve specificity.
Rephrase to third person voice: replace 'your commit workflow' with 'the commit workflow' to follow the recommended voice guidelines.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CodeRabbit CLI) and a primary action (configure for local pre-commit code reviews), but doesn't list multiple concrete actions beyond 'configure' and 'fast iteration'. It's somewhat specific but not comprehensive in listing distinct capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure CodeRabbit CLI for local pre-commit code reviews and fast iteration) and 'when' (setting up local development, integrating AI review into commit workflow, testing config changes), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases like 'coderabbit dev setup', 'coderabbit local development', 'coderabbit CLI workflow', 'coderabbit pre-commit review', plus contextual terms like 'commit workflow', 'config changes', and 'AI review'. Good coverage of terms a user would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'CodeRabbit CLI' and the narrow niche of local pre-commit AI code review setup. Very 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 solid, actionable skill with excellent executable examples and clear workflow sequencing. Its main weakness is moderate verbosity — the overview could be trimmer, and the content could benefit from splitting configuration/hook examples into separate files. The error handling table and two-layer strategy diagram add genuine value.
Suggestions
Trim the overview paragraph — Claude doesn't need an explanation of what CLI code review is or how it compares to the GitHub App.
Consider extracting the git hook script and VS Code tasks.json into separate bundle files referenced from the main skill, reducing the monolithic feel.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements: the ASCII diagram for the two-layer strategy is nice but somewhat verbose, the overview paragraph explains what CLI reviews are (Claude knows this), and the 'Output' section restates what was already covered. The error handling table and code examples are well-structured though. | 2 / 3 |
Actionability | Excellent actionability throughout — every step has fully executable, copy-paste ready code including bash scripts with proper shebangs and error handling (set -euo pipefail), YAML configuration, and JSON task definitions. Commands are specific and complete. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from installation through verification, local review, hook integration, configuration, and IDE setup. The pre-push hook includes both blocking and non-blocking patterns with explicit decision points. The error handling table provides a clear feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's somewhat monolithic — the git hook script, VS Code tasks, and configuration could be split into separate referenced files. The reference to 'coderabbit-sdk-patterns' in Next Steps is good but there are no bundle files to support it. For a skill of this length (~120 lines of content), some splitting would improve scannability. | 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 | |
3a2d27d
Table of Contents
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.