caveman-commit

Generates terse Conventional Commits messages from staged changes.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/TrayMachi/dotfiles --skill caveman-commit-traymachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/TrayMachi/dotfiles/tree/main/agents/skills/caveman-commit
Command: npx skills add https://github.com/TrayMachi/dotfiles --skill caveman-commit-traymachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing commit messages often produces verbose, inconsistent, or filler-heavy text that obscures intent. This Skill generates concise Conventional Commits messages that preserve the reasoning behind a change while cutting noise like AI attribution, restated diffs, and unnecessary body text. ## Core Features & Use Cases - Conventional Commits formatting: Produces subjects in <type>(<scope>): <imperative summary> form with types like feat, fix, refactor, and revert, capped at 50-72 characters. - Selective body generation: Adds a wrapped body only when the why is non-obvious, and always for breaking changes, security fixes, data migrations, and reverts. - Use Case: After staging a breaking API rename, ask for a commit message and receive feat(api)!: rename /v1/orders to /v1/checkout with a BREAKING CHANGE footer explaining the migration deadline. ## Quick Start Ask the assistant to write a commit message for your staged changes and it will output a ready-to-paste Conventional Commits message.

Frequently Asked Questions about caveman-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good Conventional Commits message?

Use the format type(scope): imperative summary, keeping the subject under 50 characters with a hard cap of 72. Add a body only when the why is non-obvious, and always include one for breaking changes, security fixes, migrations, and reverts.

How to generate a commit message from staged changes?

Invoke the skill with a phrase like write a commit or generate commit after staging your changes. It outputs only the message as a code block ready to paste, without staging, committing, or amending anything itself.

When should a commit message include a body?

Include a body when the reason for the change is not obvious from the subject, and always for breaking changes, security fixes, data migrations, and reverts. Wrap body lines at 72 characters and reference issues at the end with lines like Closes #42.

Does this tool run git commit automatically?

No, it only generates the commit message text. It does not stage files, run git commit, or amend existing commits, so you paste the output into your own git workflow.

What should never appear in a commit message?

Avoid phrases like this commit does X, first-person pronouns, AI attribution lines, and emoji unless the project convention uses them. Do not restate file names already covered by the scope.