caveman-review
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 strong skill description that clearly communicates its unique value proposition (compressed, noise-free code review), specifies the exact output format, and provides comprehensive trigger terms. It uses third person voice correctly and is concise without being vague. The explicit 'Use when' clause with multiple natural trigger phrases makes it easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: cuts noise from PR feedback, preserves actionable signal, formats each comment as one line with location/problem/fix. Describes a specific output format and methodology. | 3 / 3 |
Completeness | Clearly answers both what (ultra-compressed code review comments with location/problem/fix format) and when (explicit 'Use when' clause with multiple trigger phrases plus auto-trigger condition). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'review this PR', 'code review', 'review the diff', '/review', '/caveman-review', 'pull requests'. These are terms users would naturally say when requesting code review. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: ultra-compressed, one-line format code review. The specific format constraint (location, problem, fix) and the unique '/caveman-review' command clearly distinguish it from generic code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that exemplifies concise, actionable instruction. The before/after examples are particularly effective at demonstrating the desired transformation. The Auto-Clarity escape hatch for security findings and onboarding contexts shows thoughtful design, and the Boundaries section cleanly scopes the skill's responsibilities.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what code review is or how PRs work. Every section earns its place: format spec, severity prefixes, drop/keep lists, examples, and edge cases. No wasted tokens. | 3 / 3 |
Actionability | Highly actionable with exact format templates (`L<line>: <problem>. <fix>.`), concrete severity prefixes, explicit before/after examples showing the transformation, and clear drop/keep lists. Claude knows exactly what to produce. | 3 / 3 |
Workflow Clarity | This is a single-task skill (produce terse review comments) with an unambiguous workflow: apply format, use severity prefixes when mixed, follow drop/keep rules. The Auto-Clarity section provides clear decision criteria for when to break terse mode. The Boundaries section clearly scopes what the skill does and doesn't do. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Rules, Examples, Auto-Clarity, Boundaries) with clear headers. No monolithic walls of text, no unnecessary nesting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- JuliusBrussee/caveman
- Commit
8bab5c7
- 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.