caveman-commit · git:20260908.72ec452 · 2026-09-08 · sha256 fd8461df5361d90e
caveman-commit git:20260908.72ec452A
Immutable. This exact content never changes and is served at /api/v1/blob/fd8461df5361d90e.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qqbbifn4mcqk2v52/fd8461df5361d90ed5323d2d3f59bee519c56313639a08cc3fb4160fd5b3f91b.json
Then /plugin install caveman-commit@markdownregistry-qqbbifn4mcqk2v52 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: caveman-commit description: > Write a Conventional Commits message compressed to intent only. Use for commit-message drafting or shortening and explicit /caveman-commit requests. Use as a wording helper within an authorized commit workflow. --- Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what. Read [semantic conventions](../git-hygiene/references/semantic-conventions.md) when choosing types or breaking markers. Respect explicit repository commit policy. Preserve required release-parser metadata even when compressing the message. ## Rules **Subject line:** - `<type>(<scope>)!: <imperative summary>`. Scope and `!` are optional. Use `!` for breaking changes. - 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 - ❌ "feat: add a new endpoint to get user profile information from the database" - ✅ ``` feat(api): add GET /users/:id/profile Mobile client needs profile data without the full user payload to reduce LTE bandwidth on cold-launch screens. Closes #128 ``` Diff: breaking API change - ✅ ``` feat(api)!: rename /v1/orders to /v1/checkout BREAKING CHANGE: clients on /v1/orders must migrate to /v1/checkout before 2026-06-01. Old route returns 410 after that date. ``` ## 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. For a message-only request, output the message as a code block ready to paste. Inside an authorized commit task, return the wording to the coordinating workflow so it continues staging, validation, and committing under its existing authority; do not terminate that task at message generation. "stop caveman-commit" or "normal mode": revert to verbose commit style.