CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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, lean skill that respects Claude's intelligence while providing precise, actionable constraints. The examples are concrete and illustrative, the rules are specific without being verbose, and the boundaries section clearly scopes what the skill does and doesn't do. One of the stronger skill files — it achieves high clarity in minimal token budget.

DimensionReasoningScore

Conciseness

Every line earns its place. No explanation of what Conventional Commits is or how git works. The rules are terse, the examples are tight, and the anti-patterns (❌) are single-line contrasts. No padding or unnecessary context.

3 / 3

Actionability

Provides exact format templates, concrete type lists, specific character limits, complete before/after examples with real commit messages, and clear boundary rules. Claude can immediately generate correct output from this.

3 / 3

Workflow Clarity

This is a single-task skill (generate a commit message) with an unambiguous sequence: read diff → apply rules → output code block. The decision tree for when to include a body vs. subject-only is explicit, and the 'Auto-Clarity' section serves as a validation checkpoint for critical cases.

3 / 3

Progressive Disclosure

For a standalone 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 or unnecessary nesting.

3 / 3

Total

12

/

12

Passed

Description

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 key criteria. It clearly communicates what the skill does (generates ultra-compressed commit messages in Conventional Commits format), specifies concrete constraints (≤50 chars subject, conditional body), and provides comprehensive trigger terms including natural language phrases, slash commands, and auto-trigger conditions. The distinctive 'caveman' branding and specific formatting rules make it easily distinguishable from other potential commit-related skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: generates commit messages, cuts noise while preserving intent/reasoning, uses Conventional Commits format, enforces subject ≤50 chars constraint, includes body only when 'why' isn't obvious.

3 / 3

Completeness

Clearly answers both 'what' (ultra-compressed commit message generator with Conventional Commits format, subject ≤50 chars, body only when needed) 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', and 'staging changes'. These are phrases users would naturally say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: commit message generation with a specific style (ultra-compressed, caveman). The unique slash commands and specific format constraints make it unlikely to conflict with other skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
juliusbrussee/caveman
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.