1. Habit
  2. Skills
  3. Caveman Commit skill
Julius Brussee · 411K installs

Caveman Commit skill
Runs by itself, commit message requested.

Every commit message short and exact.

Install the Caveman Commit skill and make it a habit: follow https://gethabit.dev/skills/juliusbrussee/caveman-commit.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

411K installs114K starsApache-2.0 licenceSource on GitHub ↗

Caveman Commit

by Julius Brussee · 411K installs

The skill

The caveman commit skill writes short Conventional Commits messages that state intent only: imperative subject, allowed type and optional scope, a body only when needed, no filler.

Only when you ask.

The habit

Every commit message short and exact.

↻ Runs by itselfcommit message requested

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

commit message requested. Runs in Claude Code.

  • ↻ commit message requested
  • /commit or /caveman-commit

02

It checks its work

format rules check. If a check fails, it tries again.

  • ✓subject matches <type>(<scope>): <summary> with an allowed type
  • ✓subject is at most 72 characters with no trailing period
  • ✓body lines wrap at 72 characters
  • ✓breaking changes, security fixes, data migrations and reverts include a body

03

It remembers

past commit messages. The next run reads it first: project capitalization and scope conventions from recent commits.

loops/terse-commit-message-loop/notes.md

One run, step by step.
Then it stops.

Stop ruleStops after one commit message per request.

  1. 01

    Read the diff

    The agent looks at what changed and why.

  2. 02

    Pick type and scope

    It picks feat, fix, refactor, perf, docs, test, chore, build, ci, style or revert, plus an optional scope.

  3. 03

    Write the subject

    It writes an imperative summary, aiming for 50 characters and never above 72.

  4. 04

    Decide on a body

    It adds a body only for a non-obvious why, breaking change, migration note or linked issue.

  5. 05

    Strip filler

    It removes phrases like this commit, I or we, emoji, and AI attribution unless your own rule asks for a trailer.

  6. 06

    Hand over

    It outputs the message as a code block to paste, without staging or committing.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Caveman Commit skill helps.

Use it when

  • ✓ You want a commit message for staged changes
  • ✓ Your project uses Conventional Commits
  • ✓ You want why over what in history

Skip it when

  • – You want the agent to run git commit itself
  • – Your project uses a different commit format

Questions

Caveman Commit skill, answered.

Does it run git commit?

No. It only writes the message; staging, committing and amending stay with you.

How do I turn it off?

Say stop caveman-commit or normal mode to go back to a verbose style.

How do I install the Caveman Commit skill?

Copy the prompt at the top into your agent. It installs the skill from JuliusBrussee/caveman and sets up the habit. Or run npx skills add JuliusBrussee/caveman --skill caveman-commit.

Is the Caveman Commit skill free?

Yes. It is published under Apache-2.0. Habit is free too.

Caveman Commit. Now as a habit.

Install the Caveman Commit skill and make it a habit: follow https://gethabit.dev/skills/juliusbrussee/caveman-commit.md

  • Free
  • No account
  • Undo in one line

All Julius Brussee skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by Julius Brussee, published under Apache-2.0. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.