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
- 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: 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.4---56Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.78## Rules910**Subject line:**11- `<type>(<scope>): <imperative summary>` — `<scope>` optional12- Types: `feat`, `fix`, `refactor`, `perf`, `docs`, `test`, `chore`, `build`, `ci`, `style`, `revert`13- Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"14- ≤50 chars when possible, hard cap 7215- No trailing period16- Match project convention for capitalization after the colon1718**Body (only if needed):**19- Skip entirely when subject is self-explanatory20- Add body only for: non-obvious *why*, breaking changes, migration notes, linked issues21- Wrap at 72 chars22- Bullets `-` not `*`23- Reference issues/PRs at end: `Closes #42`, `Refs #17`2425**What NEVER goes in:**26- "This commit does X", "I", "we", "now", "currently" — the diff says what27- "As requested by..." — use Co-authored-by trailer28- "Generated with Claude Code" or any AI attribution29- Emoji (unless project convention requires)30- Restating the file name when scope already says it3132## Examples3334Diff: new endpoint for user profile with body explaining the why35- ❌ "feat: add a new endpoint to get user profile information from the database"36- ✅37 ```38 feat(api): add GET /users/:id/profile3940 Mobile client needs profile data without the full user payload41 to reduce LTE bandwidth on cold-launch screens.4243 Closes #12844 ```4546Diff: breaking API change47- ✅48 ```49 feat(api)!: rename /v1/orders to /v1/checkout5051 BREAKING CHANGE: clients on /v1/orders must migrate to /v1/checkout52 before 2026-06-01. Old route returns 410 after that date.53 ```5455## Auto-Clarity5657Always 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.5859## Boundaries6061Only 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.
HoangNguyen0403