PluginBench
Skill
Pass
Audit score 90

caveman-commit

juliusbrussee/caveman

Write terse, Conventional Commits messages focused on intent, not description.

SourceView on skills.sh

What is caveman-commit?

Generates concise commit messages in Conventional Commits format, emphasizing the why over the what. Use when you need a commit message that follows strict formatting rules and avoids common pitfalls like restating diffs or adding unnecessary attribution.

  • Formats commit messages as `<type>(<scope>): <summary>` with types like feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert
  • Enforces imperative mood ("add", "fix") and keeps subject lines ≤50 chars (hard cap 72)
  • Generates body text only when needed: non-obvious why, breaking changes, migrations, or linked issues
  • Strips fluff: no "this commit does", no "I/we/now", no AI attribution unless user's project requires it, no emoji unless convention demands
  • Outputs message as a code block ready to paste—does not run git commit or stage files
  • Supports breaking-change notation with `!` and BREAKING CHANGE trailer for API-incompatible updates

How to install caveman-commit

npx skills add https://github.com/juliusbrussee/caveman --skill caveman-commit
Claude Code
Cursor
Windsurf
Cline

How to use caveman-commit

  1. 1.Invoke with /caveman-commit, /commit, or "write a commit message"
  2. 2.Describe the change and its context; the skill will format it
  3. 3.Review the generated message in the code block
  4. 4.Copy and paste into your git commit or amend workflow
  5. 5.Say "stop caveman-commit" or "normal mode" to return to verbose commit style

Use cases

Good for
  • Generate a commit message for a new feature with context on why it was needed
  • Write a breaking-change commit that documents migration requirements and deadlines
  • Create a terse fix message for a bug without restating what the diff already shows
  • Document a refactor with explanation of performance or maintainability gains
  • Commit a security fix with necessary context for future audits
Who it's for
  • Developers following Conventional Commits conventions
  • Teams using automated changelog generation from commit history
  • Projects requiring concise, searchable commit messages
  • Anyone tired of verbose or redundant commit messages

caveman-commit FAQ

Does this run git commit for me?

No. It only generates the message as a code block. You paste it into your git workflow manually.

What if my project uses emoji in commits?

The skill skips emoji by default. If your project convention requires them, add that context and the skill will include them.

Should I add a body for every commit?

No. Body is only for non-obvious why, breaking changes, migrations, or linked issues. Self-explanatory diffs stay subject-only.

Can I add AI attribution like 'Generated with Claude Code'?

Only if your project's own rules require an Assisted-by or AI-attribution trailer. Otherwise, the skill omits it.

How do I revert to normal commit messages?

Say 'stop caveman-commit' or 'normal mode' to switch back to verbose commit style.

Full instructions (SKILL.md)

Source of truth, from juliusbrussee/caveman.


name: caveman-commit description: > Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.

Rules

Subject line:

  • <type>(<scope>): <imperative summary> — <scope> optional
  • Types: feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert
  • Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"
  • ≤50 chars when possible, hard cap 72
  • No trailing period
  • Match project convention for capitalization after the colon

Body (only if needed):

  • Skip entirely when subject is self-explanatory
  • Add body only for: non-obvious why, breaking changes, migration notes, linked issues
  • Wrap at 72 chars
  • Bullets - not *
  • Reference issues/PRs at end: Closes #42, Refs #17

What NEVER goes in:

  • "This commit does X", "I", "we", "now", "currently" — the diff says what
  • "As requested by..." — use Co-authored-by trailer
  • "Generated with Claude Code" or any AI attribution — unless the user's own rule requires an Assisted-by/AI-attribution trailer, then add it as a trailer
  • Emoji (unless project convention requires)
  • Restating the file name when scope already says it

Examples

Diff: new endpoint for user profile with body explaining the why

  • ❌ "feat: add a new endpoint to get user profile information from the database"
  • ✅
    feat(api): add GET /users/:id/profile
    
    Mobile client needs profile data without the full user payload
    to reduce LTE bandwidth on cold-launch screens.
    
    Closes #128
    

Diff: breaking API change

  • ✅
    feat(api)!: rename /v1/orders to /v1/checkout
    
    BREAKING CHANGE: clients on /v1/orders must migrate to /v1/checkout
    before 2026-06-01. Old route returns 410 after that date.
    

Auto-Clarity

Always include body for: breaking changes, security fixes, data migrations, anything reverting a prior commit. Never compress these into subject-only — future debuggers need the context.

Boundaries

Only generates the commit message. Does not run git commit, does not stage files, does not amend. Output the message as a code block ready to paste. "stop caveman-commit" or "normal mode": revert to verbose commit style.