caveman-commit

Generate terse Conventional Commit messages from change descriptions.

Updated Aug 27, 2026

Search Tags:#git #conventional commits #release notes #commit message #breaking change #changelog hygiene

Ready to run

npx skills add https://github.com/ebarroso12/personal-skills --skill caveman-commit-ebarroso12

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/ebarroso12/personal-skills/tree/main/caveman-commit
Command: npx skills add https://github.com/ebarroso12/personal-skills --skill caveman-commit-ebarroso12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of writing noisy, inconsistent commit messages by turning your intent into a terse Conventional Commits line with optional context.

Core Features & Use Cases

Conventional Commits formatting: Produces a <type>(<scope>): <imperative summary> subject with correct conventions and capitalization.
Smart body inclusion: Includes a body only when the why is non-obvious or when breaking changes and similar high-impact events require context.
Strict output behavior: Outputs only the commit message (no staging, no git commit, no extra commentary) and targets commands like “write a commit”, “commit message”, “generate commit”, or /caveman-commit.

Quick Start

Invoke caveman-commit by telling the assistant “/caveman-commit” along with the change details, and it will return a paste-ready Conventional Commit message.

Frequently Asked Questions about caveman-commit

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

FAQPage Schema

How do I generate a conventional commit message from a change description?▼

To generate a conventional commit message, provide your change details to the assistant. It outputs a paste-ready message with an imperative subject, correct type vocabulary, and an optional body for non-obvious reasoning.

When do I need to include a body in my conventional commit?▼

Include a conventional commit body only when the reasoning is non-obvious or for high-impact events like breaking changes, security fixes, data migrations, and reverts. The generator omits the body for standard changes to reduce commit noise.

Can I generate breaking change commit messages automatically?▼

Yes, you can automatically generate breaking change commit messages. The system enforces Conventional Commit type vocabulary and includes the required body context to properly document the high-impact event and its reasoning.

What is the best way to enforce subject length limits in git commit messages?▼

The best way to enforce subject length limits is to use a generator that applies strict wrapping rules and capitalization. It outputs only the formatted commit message, excluding extra commentary and fluff attribution.

Does this conventional commit generator output git staging commands?▼

No, the conventional commit generator outputs only the commit message text. It strictly excludes staging commands, git commit execution, and extra commentary to ensure you can just copy and paste the result.

Why does my conventional commit message include unnecessary text and attribution?▼

Unnecessary text and attribution appear when commits are written manually without strict output behavior. Using a generator excludes AI and fluff attribution, outputting only the clean conventional commit message.