caveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
100
100%
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 an excellent skill description that hits all the marks. It provides specific capabilities (compressed format, Conventional Commits, character limits), comprehensive trigger terms covering natural user phrases and slash commands, and a clear 'Use when' clause. The distinctive 'caveman-commit' branding and specific formatting constraints make it easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Ultra-compressed commit message generator', 'Cuts noise from commit messages while preserving intent and reasoning', 'Conventional Commits format', 'Subject ≤50 chars', 'body only when why isn't obvious'. These are highly specific and actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (compressed commit message generator with Conventional Commits format, subject ≤50 chars, body only when why isn't obvious) 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: 'write a commit', 'commit message', 'generate commit', '/commit', '/caveman-commit', 'staging changes'. These are exactly what users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: commit message generation with a specific style (ultra-compressed, caveman). The unique '/caveman-commit' command and specific formatting constraints (≤50 chars, Conventional Commits) clearly distinguish it from general git skills or other commit message tools. | 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, tightly written skill that exemplifies token efficiency while remaining fully actionable. The rules are precise and well-structured, the examples demonstrate both good and bad patterns with realistic diffs, and the boundaries section clearly constrains behavior. The only minor note is the time-sensitive date in the breaking change example (2026-06-01), but it's used illustratively within an example rather than as an instruction, so it's acceptable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanation of what commits are or how git works. Rules are terse bullet points. The anti-patterns list is especially efficient — it tells Claude what to avoid without belaboring why. | 3 / 3 |
Actionability | Provides concrete format templates, specific type lists, exact character limits, and fully formed commit message examples with both good and bad versions. The examples are copy-paste ready and demonstrate real scenarios including breaking changes. | 3 / 3 |
Workflow Clarity | This is a single-task skill (generate a commit message) with an unambiguous workflow: read diff, apply rules, output code block. The decision tree for when to include a body vs. subject-only is explicit. 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) that are easy to scan. 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
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.