From caveman
Generates ultra-compressed Conventional Commits messages with ≤50 char subject and body only when 'why' isn't obvious. Auto-triggers when staging changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/caveman:caveman-commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.
Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.
Subject line:
<type>(<scope>): <imperative summary> — <scope> optionalfeat, fix, refactor, perf, docs, test, chore, build, ci, style, revertBody (only if needed):
- not *Closes #42, Refs #17What NEVER goes in:
Assisted-by/AI-attribution trailer, then add it as a trailerDiff: new endpoint for user profile with body explaining the why
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.
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.
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.
npx claudepluginhub juliusbrussee/caveman --plugin cavemanGenerates one-shot Conventional Commits messages for staged git changes: feat/fix/refactor types, imperative ≤50 char subjects, optional scopes and Why explanations.
Generates ultra-compressed Conventional Commits messages emphasizing 'why' over 'what', ≤50 char subjects in Japanese/English matching repo history. Activates on staged changes or via /genshijin-commit, /commit.
Generates concise conventional git commit messages prioritizing 'why' over 'what', with proper types, scopes, imperative mood, and atomic structure. Use when writing commits or learning best practices.