One-click install
npx skills add https://github.com/afonsoft/gamehub --skill caveman-commit-afonsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/afonsoft/gamehub/tree/main/.claude/skills/caveman-commit
Command: npx skills add https://github.com/afonsoft/gamehub --skill caveman-commit-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing commit messages often produces verbose, inconsistent, or filler-heavy text that obscures intent. This Skill generates concise Conventional Commits messages that preserve the reasoning behind a change while cutting noise. ## Core Features & Use Cases - Conventional Commits formatting: Produces <type>(<scope>): <imperative summary> subjects with a 50-character target and 72-character hard cap. - Context-aware bodies: Adds a body only when the why is non-obvious, and always for breaking changes, security fixes, data migrations, and reverts. - Noise elimination: Excludes AI attribution, emoji, first-person narration, and restatements of the diff. - Use Case: After staging a diff that renames a public API route, ask for a commit message and receive a subject with the ! breaking-change marker plus a BREAKING CHANGE: footer explaining the migration deadline. ## Quick Start Ask the assistant to write a commit message for the current staged diff using caveman-commit.

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 good Conventional Commits message?▼

Use the format type(scope): imperative summary, keeping the subject under 50 characters with a hard cap of 72. Add a body only when the reason for the change is not obvious from the diff, and reference issues at the end with lines like Closes #42.

How to write a commit message for a breaking change?▼

Mark the subject with an exclamation point after the type or scope, such as feat(api)!: rename /v1/orders to /v1/checkout. Always include a body with a BREAKING CHANGE: footer explaining the migration path and deadline.

When should a commit message include a body?▼

Include a body only when the why is non-obvious, or always for breaking changes, security fixes, data migrations, and reverts. Skip the body entirely when the subject line is self-explanatory.

Does this skill 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.

When should I not use this commit message style?▼

Do not use it for merge commits or automated release messages, as stated in its boundaries. Projects requiring verbose or differently formatted commit conventions should also use their own style instead.