caveman-commit

SkillCommunication

This skill makes your AI write in a short, simplified style that cuts token usage by about 65%. Tokens are the bits of text your AI reads and writes, so fewer tokens means leaner prompts and responses in every exchange. Your AI keeps handling your requests, just with far fewer words.

Available today. Use it from your connected AI after setup.

Add the skill and keep working as usual; your AI will write its prompts and responses in the short style from then on. Keep an eye on your token usage to see the difference.

Then ask your AI: use the caveman-commit skill

What your AI can do with it

  • Write prompts in a short, simplified style
  • Keep responses brief and to the point
  • Cut token usage by about 65%
  • Use fewer tokens in coding sessions and everyday tasks

What this skill tells your AI

The instructions your AI receives, as published by debuglebowski/slayzone in .agents/skills/caveman-commit/SKILL.md and read by ahel’s review.

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.

Signals

GitHub stars
192
Forks
42
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
caveman-commit
Source
github.com/debuglebowski/slayzone