caveman-commit

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

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill caveman-commit-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/caveman-commit
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill caveman-commit-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Commit messages often become bloated with filler phrases, redundant context, and inconsistent formatting, making git history hard to scan and debug. This Skill produces ultra-compressed, intent-preserving commit messages that follow the Conventional Commits specification. ## Core Features & Use Cases - Conventional Commits Enforcement: Generates subjects in <type>(<scope>): <imperative summary> format with types like feat, fix, refactor, and perf, capped at 50-72 characters. - Noise Elimination: Strips filler such as "This commit does X", AI attribution, emoji, and first-person language while preserving the reasoning behind changes. - Contextual Body Rules: Adds a body only for non-obvious rationale, breaking changes, security fixes, migrations, and issue references like Closes #42. - Use Case: After staging a breaking API rename, ask for a commit message and receive a subject with the ! breaking-change marker plus a migration-note body 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>` with types like 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 subject is not self-explanatory: non-obvious reasoning, breaking changes, security fixes, data migrations, or reverts of prior commits. Wrap body lines at 72 characters and reference issues at the end with trailers like `Closes #42`.

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

Append an exclamation mark after the type or scope, such as `feat(api)!: rename /v1/orders to /v1/checkout`, and include a `BREAKING CHANGE:` note in the body describing the migration path and deadlines.

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 retain 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 generation attribution, and emoji unless project convention requires them. Use a Co-authored-by trailer instead of "As requested by" phrasing.