skills.rest
marketiv-id
marketiv-idOFFICIAL
Explore all skills by this author →
GitHub

caveman-commit

Generates terse Conventional Commits messages from staged changes with strict formatting rules.

Updated Feb 24, 2026
Search Tags:#git#code review#version control#conventional commits#commit message#generate#breaking change
One-click install
npx skills add https://github.com/marketiv-id/marketiv-web --skill caveman-commit-marketiv-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/marketiv-id/marketiv-web/tree/main/.qwen/skills/caveman-commit
Command: npx skills add https://github.com/marketiv-id/marketiv-web --skill caveman-commit-marketiv-id

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing commit messages often produces verbose, inconsistent, or vague text that obscures intent. This Skill generates concise Conventional Commits messages that preserve the reasoning behind a change while cutting filler, making git history easier to scan and debug. ## Core Features & Use Cases - Conventional Commits Formatting: Produces subjects in <type>(<scope>): <imperative summary> form with a 50-character target and 72-character hard cap. - Context-Aware Bodies: Adds a body only when the why is non-obvious, and always for breaking changes, security fixes, data migrations, and reverts. - Noise Elimination: Strips AI attribution, emoji, first-person narration, and restated file names from messages. - Use Case: After staging a breaking API rename, invoke the Skill to receive a ready-to-paste message like 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 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, keeping the subject under 50 characters with a hard cap of 72. Valid types include feat, fix, refactor, perf, docs, test, chore, build, ci, style, and revert. Add a body only when the reasoning is not obvious from the diff.

When should a commit message include a body?▼

Include a body only when the why is non-obvious, or when linking issues and migration notes. Bodies are always required for breaking changes, security fixes, data migrations, and reverts so future debuggers have the necessary context.

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

Append an exclamation mark after the type or scope, such as feat(api)!:, and add a BREAKING CHANGE footer in the body. The footer should explain what consumers must migrate and any relevant deadline.

Does this Skill run git commit or stage files?▼

No. It only generates the commit message text and outputs it as a code block ready to paste. It does not stage files, run git commit, or amend existing commits.

What should never appear in a commit message?▼

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

Related Skills

Explore More Software Engineering Skills→
ClaudfatherClaudfather

ship

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

Official
Intermediate
hoanghn61hoanghn61

github-workflow

Automate Git branching, committing, PRs, issues, and code review workflows via gh CLI.

Community
Intermediate
anilcan-karaanilcan-kara

requesting-code-review

Run pre-commit verification with security scans, quality gates, and auto-fix loops.

Community
Advanced
h1km4t1ll0h1km4t1ll0
37

make-commits-great-again

Generate Trump-style commit messages from the current git diff.

Community
Intermediate