Back to skills

Agent Skill

Caveman Commit

caveman-commit

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.

JuliusbrusseeToolsJavaScriptAiAnthropicCavemanClaudeClaude-codeLlmMemePrompt-engineeringSkillTokens
github.com/juliusbrussee/caveman/tree/main/skills/caveman-commit

178K installs

•

juliusbrussee/caveman

•

by Juliusbrussee

Score

9.0

/ 10

Installs

178K

Repo Stars

75.7K

Last Updated

9d ago

Fresh

Quality Ratio

100%

Description

Verified

Language

JavaScript

First Published

Apr 2026

Summary

The Caveman Commit agent skill generates concise, high-signal commit messages following the Conventional Commits specification, prioritizing intent and reasoning over superficial details. This agent skill is ideal for developers and teams who value a clean, standardized Git history and adhere to the Conventional Commits specification. It is a well-adopted skill with solid traction in the registry. It enforces a strict Conventional Commits format, requiring a subject line with an imperative summary (e.g., `feat: add`) under 50 characters, and a body only for non-obvious 'why,' breaking changes, or linked issues. The skill explicitly prevents common commit message anti-patterns such as personal pronouns, AI attributions, or redundant descriptions, while ensuring context is preserved for critical changes like security fixes or data migrations. It activates automatically when a user requests a commit message or has staged changes, providing a message formatted for direct pasting without performing Git operations. However, it strictly generates the message content in a code block and does not execute Git commands or stage files.

Skill Definition

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

  • ❌ "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. Output the message as a code block ready to paste. "stop caveman-commit" or "normal mode": revert to verbose commit style.

How to Use

Use in O-mega

Claude Code

npx skills add juliusbrussee/caveman caveman-commit