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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is caveman-commit in JuliusBrussee/caveman

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplar of terse, high-signal instruction design: concrete rules, executable examples, explicit guardrails, and clean sectioning with no bloat. It assumes Claude's competence throughout.

DimensionReasoningScore

Conciseness

The body is lean and 'caveman'-terse — 'Write commit messages terse and exact. No fluff. Why over what.' — with no explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

Concrete, copy-paste-ready guidance: enumerated types, char limits, imperative-mood rules, and full before/after commit examples with body and trailers, all directly executable.

3 / 3

Workflow Clarity

A simple single-task skill whose action is unambiguous — 'Output the message as a code block ready to paste' — with explicit non-destructive Boundaries (no commit, stage, or amend), so the simple-skill exception applies and no validation checkpoint is required.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; content is organized into well-signaled sections (Rules, Examples, Auto-Clarity, Boundaries) with no nested references, satisfying the simple-skill progressive-disclosure criterion.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and concise while explicitly covering both capability and trigger conditions. It avoids fluff and over-claims, and its named triggers make it highly distinguishable.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and constraints — 'Ultra-compressed commit message generator', 'Cuts noise from commit messages while preserving intent', 'Conventional Commits format', 'Subject ≤50 chars', 'body only when why isn't obvious' — matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (terse Conventional Commits generator with stated constraints) and when (an explicit 'Use when...' clause with concrete triggers), matching the top anchor.

3 / 3

Trigger Term Quality

Explicit natural triggers users would say — 'write a commit', 'commit message', 'generate commit', '/commit', '/caveman-commit', plus 'Auto-triggers when staging changes' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Narrow niche (commit-message generation only) with distinct, specific triggers and a named slash command, making conflict with other skills unlikely.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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