caveman-commit

Generates terse Conventional Commits messages with imperative subjects and optional bodies.

Updated Jan 28, 2026

Search Tags:#git #version control #developer workflow #conventional commits #commit message #generate

Ready to run

npx skills add https://github.com/ttphats/project-detedxs26 --skill caveman-commit-ttphats

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, concise commit messages is tedious, and verbose or vague messages clutter git history. This Skill generates ultra-compressed commit messages in Conventional Commits format so your history stays clean and scannable. ## Core Features & Use Cases - Conventional Commits Format: Produces subjects like `feat(auth): add login redirect` with proper type, optional scope, and imperative mood. - Smart Body Rules: Adds a body only when the "why" is non-obvious, such as breaking changes, security fixes, migrations, or reverts. - Strict Style Enforcement: Subjects capped at 50-72 characters, no trailing periods, no AI attribution, no filler phrases. - Use Case: After staging changes that fix a race condition in seat locking, ask for a commit message and receive `fix(booking): prevent double-booking via redis lock` 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, where type is one of feat, fix, refactor, perf, docs, test, chore, build, ci, style, or revert. Keep the subject under 50 characters, use imperative mood like "add" or "fix", 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 subject, such as breaking changes, security fixes, data migrations, or reverts of prior commits. Wrap body lines at 72 characters and reference issues at the end with lines like Closes #42.

Does this skill run git commit automatically?▼

No, it only generates the commit message text as a code block ready to paste. It does not stage files or execute git commit, so you retain full control over when and how the commit is created.

What are the Conventional Commits subject line rules?▼

The subject must use an approved type prefix, imperative mood verbs, no trailing period, and stay at or under 50 characters when possible with a hard cap of 72. Scope in parentheses is optional.

How do I turn off the terse commit style?▼

Say "stop caveman-commit" or "normal mode" to revert to verbose commit message style. The skill only affects message generation and leaves no persistent changes to your repository.