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
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-commit
3description: >
4 Write a Conventional Commits message compressed to intent only. Use for
5 "write a commit", "commit message", /commit or /caveman-commit.
6metadata:
7 source: https://skillmd.com/skills/gabrielmoreira/caveman-commit
8---
9
10Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.
11
12## Rules
13
14**Subject line:**
15- `<type>(<scope>): <imperative summary>` — `<scope>` optional
16- Types: `feat`, `fix`, `refactor`, `perf`, `docs`, `test`, `chore`, `build`, `ci`, `style`, `revert`
17- Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"
18- ≤50 chars when possible, hard cap 72
19- No trailing period
20- Match project convention for capitalization after the colon
21
22**Body (only if needed):**
23- Skip entirely when subject is self-explanatory
24- Add body only for: non-obvious *why*, breaking changes, migration notes, linked issues
25- Wrap at 72 chars
26- Bullets `-` not `*`
27- Reference issues/PRs at end: `Closes #42`, `Refs #17`
28
29**What NEVER goes in:**
30- "This commit does X", "I", "we", "now", "currently" — the diff says what
31- "As requested by..." — use Co-authored-by trailer
32- "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
33- Emoji (unless project convention requires)
34- Restating the file name when scope already says it
35
36## Examples
37
38Diff: new endpoint for user profile with body explaining the why
39- ❌ "feat: add a new endpoint to get user profile information from the database"
40- ✅
41 ```
42 feat(api): add GET /users/:id/profile
43
44 Mobile client needs profile data without the full user payload
45 to reduce LTE bandwidth on cold-launch screens.
46
47 Closes #128
48 ```
49
50Diff: breaking API change
51- ✅
52 ```
53 feat(api)!: rename /v1/orders to /v1/checkout
54
55 BREAKING CHANGE: clients on /v1/orders must migrate to /v1/checkout
56 before 2026-06-01. Old route returns 410 after that date.
57 ```
58
59## Auto-Clarity
60
61Always 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.
62
63## Boundaries
64
65Only 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.