skills.rest
kaitoartz
kaitoartzCOMMUNITY
Explore all skills by this author →
Website𝕏@kaitoartzzGitHub

caveman-commit

Generates terse Conventional Commits messages from staged changes.

Updated Jun 30, 2026
Search Tags:#git#code review#version control#developer workflow#conventional commits#commit message#generate
One-click install
npx skills add https://github.com/kaitoartz/dotfiles --skill caveman-commit-kaitoartz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/kaitoartz/dotfiles/tree/main/dot_gemini/config/skills/caveman-commit
Command: npx skills add https://github.com/kaitoartz/dotfiles --skill caveman-commit-kaitoartz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Commit messages often become bloated with filler phrases, restated diffs, and AI attribution, making git history hard to scan. This Skill produces ultra-compressed, intent-preserving commit messages in Conventional Commits format so your history stays readable and useful for future debugging. ## Core Features & Use Cases - Conventional Commits formatting: Enforces <type>(<scope>): <imperative summary> with types like feat, fix, refactor, perf, and a subject capped at 50-72 characters. - Why-over-what bodies: Adds a body only for non-obvious reasoning, breaking changes, migrations, security fixes, and linked issues such as Closes #42. - Noise elimination: Strips phrases like "This commit does X", first-person pronouns, emoji, and AI attribution from every message. - 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 staged changes 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 good conventional commit message?▼

Use the format type(scope): imperative summary, with types like feat, fix, refactor, or perf. Keep the subject under 50 characters, use imperative mood like "add" instead of "added", and omit the trailing period.

When should a commit message include a body?▼

Add a body only when the why is not obvious from the diff, such as breaking changes, security fixes, data migrations, or reverts. Wrap body lines at 72 characters and place issue references like Closes #42 at the end.

How do I mark a breaking change in Conventional Commits?▼

Append an exclamation mark after the type or scope, like feat(api)!:, and include a BREAKING CHANGE footer in the body describing the migration path and any deadlines for consumers.

Does this skill run git commit or stage files automatically?▼

No, it only generates the commit message text as a code block ready to paste. It does not run git commit, stage files, 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, words like "now" or "currently", AI attribution lines, and emoji unless the project convention requires them. The diff already states what changed.

Related Skills

Explore More Software Engineering Skills→
AbsolutelySkilledAbsolutelySkilled
207

code-review-mastery

Review local git diffs and output MAJOR/MINOR findings.

Official
Advanced
wopal-cnwopal-cn
3

cnb-code-commit

Writes code changes, commits, pushes branches, and creates pull requests on CNB.

Official
Intermediate
constellizeconstellize
1

pre-commit-review

Enforce pre-commit quality gates with static analysis, unit tests, and security scans.

Official
Advanced
rvdbreemenrvdbreemen
199

caveman-commit

Generates formatted commit messages with optional explanatory body text.

Community
Intermediate