skills.rest
ferrarifankid04
ferrarifankid04COMMUNITY
Explore all skills by this author →
GitHub

caveman-commit

Generates terse Conventional Commits messages from staged changes.

Updated Aug 6, 2026
Search Tags:#git#code review#version control#conventional commits#commit message#commit generator
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill caveman-commit-ferrarifankid04
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/antigravity/caveman/skills/caveman-commit
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill caveman-commit-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing commit messages often produces verbose, inconsistent, or noisy text that obscures intent. This Skill generates ultra-compressed commit messages in Conventional Commits format, keeping the subject under 50 characters and including a body only when the reasoning is non-obvious. ## Core Features & Use Cases - Conventional Commits Generation: Produces <type>(<scope>): <imperative summary> subjects using types like feat, fix, refactor, perf, and revert. - Context-Aware Bodies: Adds a wrapped body only for breaking changes, security fixes, data migrations, reverts, or non-obvious reasoning, with issue references like Closes #42. - Noise Elimination: Strips AI attribution, filler phrases, emoji, and redundant restatements so the message stays terse and exact. - 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 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 Conventional Commits message?▼

Use the format type(scope): imperative summary, such as feat(api): add GET /users/:id/profile. Keep the subject under 50 characters with a hard cap of 72, use imperative mood, and add a body only when the reasoning is not obvious.

When should a commit message include a body?▼

Include a body only for non-obvious reasoning, breaking changes, security fixes, data migrations, and reverts. Skip it entirely when the subject line is self-explanatory, and reference issues at the end with lines like Closes #42.

Does this tool run git commit or stage files?▼

No, it only generates the commit message text as a ready-to-paste code block. It does not stage files, run git commit, or amend existing commits, so you stay in control of the actual git operations.

How do I mark a breaking change in a commit message?▼

Append an exclamation mark after the type or scope, like feat(api)!: rename /v1/orders to /v1/checkout, and add a BREAKING CHANGE footer in the body explaining the migration path and deadlines for consumers.

Can I turn off the terse commit style?▼

Yes, say stop caveman-commit or normal mode to revert to verbose commit message style. The skill also respects project conventions for capitalization, emoji, and AI-attribution trailers when the user's own rules require them.

Related Skills

Explore More Software Engineering Skills→
Utchash007Utchash007

commit

Stage git changes and generate conventional commit messages with confirmation.

Community
Advanced
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
shirulotshirulot

changelog-automation

Parse commit history to generate changelogs and release notes.

Community
Advanced
pjmageepjmagee
4

caveman-commit

Generate Conventional Commits with type(scope) and imperative subjects.

Community
Basic