caveman-commit

SKILL.md

Terse, conventional commit messages that prioritize reasoning over description.

Enforces Conventional Commits format with type, optional scope, and imperative subject lines capped at 50 characters

Omits body text when the diff is self-explanatory; includes it only for non-obvious reasoning, breaking changes, migrations, and issue references

Strips noise like "This commit does", first-person language, file name repetition, and AI attribution

Triggers on user commands like "write a commit", "commit message", or /caveman-commit, or auto-activates when staging changes

Generates message only; does not execute git commands or stage 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