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
- Any AI-attribution trailer ("Generated with ...", "Co-Authored-By: ")
- 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
Diff: breaking API change
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.
1---2name: caveman-commit3description: Use when the user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit, or when staging changes. Generates ultra-compressed Conventional Commits messages — subject ≤50 chars, body only when "why" isn't obvious. Cuts noise while preserving intent.4license: [object Object]5---67# Caveman Commit89Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.1011## Rules1213**Subject line:**14- `<type>(<scope>): <imperative summary>` — `<scope>` optional15- Types: `feat`, `fix`, `refactor`, `perf`, `docs`, `test`, `chore`, `build`, `ci`, `style`, `revert`16- Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"17- ≤50 chars when possible, hard cap 7218- No trailing period19- Match project convention for capitalization after the colon2021**Body (only if needed):**22- Skip entirely when subject is self-explanatory23- Add body only for: non-obvious *why*, breaking changes, migration notes, linked issues24- Wrap at 72 chars25- Bullets `-` not `*`26- Reference issues/PRs at end: `Closes #42`, `Refs #17`2728**What NEVER goes in:**29- "This commit does X", "I", "we", "now", "currently" — the diff says what30- "As requested by..." — use Co-authored-by trailer31- Any AI-attribution trailer ("Generated with ...", "Co-Authored-By: <AI>")32- Emoji (unless project convention requires)33- Restating the file name when scope already says it3435## Examples3637Diff: new endpoint for user profile with body explaining the why38- Bad: "feat: add a new endpoint to get user profile information from the database"39- Good:40 ```41 feat(api): add GET /users/:id/profile4243 Mobile client needs profile data without the full user payload44 to reduce LTE bandwidth on cold-launch screens.4546 Closes #12847 ```4849Diff: breaking API change50- Good:51 ```52 feat(api)!: rename /v1/orders to /v1/checkout5354 BREAKING CHANGE: clients on /v1/orders must migrate to /v1/checkout55 before 2026-06-01. Old route returns 410 after that date.56 ```5758## Auto-Clarity5960Always 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.6162## Boundaries6364Only 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.
danmestas