Caveman Commit

Strips commit messages down to signal only. Enforces Conventional Commits with a hard line on fluff: no "this commit does", no AI attribution, no restating what the diff already shows. Subject lines stay under 50 characters when possible, bodies appear only when the "why" isn't obvious from context. It auto-triggers when you stage changes and understands natural invocations like "write a commit" or "/commit". The examples are solid, the breaking change format is clear, and the auto-clarity rule for security fixes and migrations is the kind of guardrail that saves future you from archaeology work. If your team's commit log reads like a legal document, this will fix that.

GitHub stars: 504
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill caveman-commit --agent claude-code

Installs into .claude/skills of the current project.

Files

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: