skills.rest
camercu
camercuCOMMUNITY
Explore all skills by this author →
GitHub

caveman-commit

Generates terse Conventional Commits messages from staged changes without committing.

2|2|Updated Jun 28, 2015
Search Tags:#git#code review#version control#conventional commits#commit message#generate
One-click install
npx skills add https://github.com/camercu/dotfiles --skill caveman-commit-camercu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/camercu/dotfiles/tree/main/common/.config/agents/skills/caveman-commit
Command: npx skills add https://github.com/camercu/dotfiles --skill caveman-commit-camercu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing commit messages that are both concise and informative is hard: developers either write vague one-liners or verbose paragraphs. This Skill produces Conventional Commits messages that capture intent (the why) in a strict, reviewable format. ## Core Features & Use Cases - Conventional Commits formatting: Generates <type>(<scope>): <imperative summary> subjects with types like feat, fix, refactor, capped at 50-72 characters. - Intent-focused bodies: Adds a body only when the why is non-obvious, and always for breaking changes, security fixes, data migrations, and reverts. - No fluff policy: Strips AI attribution, filler phrases, and emoji unless project convention requires them. - 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 ready to paste. ## Quick Start Ask the AI to write a commit message for your current staged diff using the caveman-commit style.

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 Conventional Commits message?▼

Use the format `<type>(<scope>): <imperative summary>` with types like feat, fix, refactor, or chore. Keep the subject under 50 characters when possible, use imperative mood like "add" or "fix", and add a body only when the reason for the change is non-obvious.

How to write a commit message for a breaking change?▼

Mark breaking changes with an exclamation after the type or scope, like `feat(api)!: rename /v1/orders to /v1/checkout`, and always include a `BREAKING CHANGE:` footer in the body explaining migration steps and deadlines.

When should a commit message include a body?▼

Add a body only when the subject is not self-explanatory: non-obvious reasoning, breaking changes, migration notes, or linked issues. Bodies are mandatory for security fixes, data migrations, and reverts so future debuggers have context.

Does caveman-commit run git commit automatically?▼

No, it only generates the commit message text as a code block ready to paste. It does not stage files, run git commit, or amend existing commits, so you keep full control over the git operation.

What should never appear in a commit message?▼

Avoid filler like "this commit does X", first-person pronouns, AI attribution lines, and emoji unless the project convention requires them. Restating file names already covered by the scope is also discouraged.

Related Skills

Explore More Software Engineering Skills→
ClaudfatherClaudfather

ship

Commits verified changes and opens pull requests via git and GitHub CLI.

Official
Intermediate
eriknovakeriknovak

commit-pr

Create a conventional commit, push the branch, and open a GitHub pull request.

Community
Advanced
l3ochol3ocho

changelog-format

Parse Conventional Commits and Keep a Changelog formats to generate release notes.

Community
Intermediate
rvdbreemenrvdbreemen
199

caveman-commit

Generates formatted commit messages with optional explanatory body text.

Community
Intermediate