Generates terse Conventional Commits messages from staged changes.
npx skills add https://github.com/th-efool/SKILLS --skill caveman-commit-th-efool
Please help me install this Agent Skill. Skill: caveman-commit Source: https://github.com/th-efool/SKILLS/tree/main/caveman-commit Command: npx skills add https://github.com/th-efool/SKILLS --skill caveman-commit-th-efool
<type>(<scope>): <imperative summary> format with types like feat, fix, refactor, and perf, capped at 50-72 characters. - Context-Aware Bodies: Adds a body only when the why is non-obvious, and always requires one for breaking changes, security fixes, data migrations, and reverts. - Noise Elimination: Strips AI attribution, first-person language, emoji, and restatements of the diff, keeping only issue references like Closes #42. - Use Case: After staging a breaking API rename, invoke the Skill to get feat(api)!: rename /v1/orders to /v1/checkout with a BREAKING CHANGE footer explaining the migration deadline. ## Quick Start Ask the AI to write a commit message for your staged changes using the caveman-commit skill.High-intent search queries and answers about installing and using this skill.
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" instead of "added", and omit the trailing period.
Add a body only when the why is non-obvious, or for breaking changes, security fixes, data migrations, and reverts. Skip it entirely when the subject is self-explanatory, and reference issues at the end with lines like `Closes #42`.
Append an exclamation mark after the type or scope, such as `feat(api)!: rename /v1/orders to /v1/checkout`, and include a `BREAKING CHANGE:` footer in the body explaining the migration path and deadline for consumers.
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, so you stay in control of the actual git operations.
Avoid phrases like "this commit does X", first-person pronouns, words like "now" or "currently", AI attribution lines, and emoji unless the project convention requires them. The diff already shows what changed, so the message should focus on why.
HirogaKatageriConvert git diffs into Conventional Commits messages with optional bodies and footers.
wopal-cnWrites code changes, commits, pushes branches, and creates pull requests on CNB.
shirulotParse commit history to generate changelogs and release notes.
hypershift-communityEnforce Conventional Commit formatting for HyperShift Git commits.