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 lean-commit" or "normal mode": revert to verbose commit style.
1---2name: lean-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 /prompt-studio:lean-commit. Offer it when the user stages changes.4license: Apache-2.05---67Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.89## Rules1011**Subject line:**12- `<type>(<scope>): <imperative summary>` — `<scope>` optional13- Types: `feat`, `fix`, `refactor`, `perf`, `docs`, `test`, `chore`, `build`, `ci`, `style`, `revert`14- Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"15- ≤50 chars when possible, hard cap 7216- No trailing period17- Match project convention for capitalization after the colon1819**Body (only if needed):**20- Skip entirely when subject is self-explanatory21- Add body only for: non-obvious *why*, breaking changes, migration notes, linked issues22- Wrap at 72 chars23- Bullets `-` not `*`24- Reference issues/PRs at end: `Closes #42`, `Refs #17`2526**What NEVER goes in:**27- "This commit does X", "I", "we", "now", "currently" — the diff says what28- "As requested by..." — use Co-authored-by trailer29- "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 trailer30- Emoji (unless project convention requires)31- Restating the file name when scope already says it3233## Examples3435Diff: new endpoint for user profile with body explaining the why36- ❌ "feat: add a new endpoint to get user profile information from the database"37- ✅38 ```39 feat(api): add GET /users/:id/profile4041 Mobile client needs profile data without the full user payload42 to reduce LTE bandwidth on cold-launch screens.4344 Closes #12845 ```4647Diff: breaking API change48- ✅49 ```50 feat(api)!: rename /v1/orders to /v1/checkout5152 BREAKING CHANGE: clients on /v1/orders must migrate to /v1/checkout53 before 2026-06-01. Old route returns 410 after that date.54 ```5556## Auto-Clarity5758Always 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.5960## Boundaries6162Only 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 lean-commit" or "normal mode": revert to verbose commit style.
utk2103