caveman-commit

Generate terse Conventional Commit messages from staged diffs.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/darkmatter/skills --skill caveman-commit-darkmatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/darkmatter/skills/tree/main/skills/caveman-commit
Command: npx skills add https://github.com/darkmatter/skills --skill caveman-commit-darkmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill strips commit messaging down to the essentials, helping you turn a diff or change request into a clean, conventional commit message without unnecessary wording.

Core Features & Use Cases

  • Conventional Commits Formatting: Produces subjects in the expected type-scope-summary structure for consistent history and automation.
  • Terse, Exact Summaries: Keeps the subject short, imperative, and focused on the change rather than the process.
  • Smart Body Guidance: Adds a body only when the reason, breaking change, migration, or revert context is not obvious.
  • Use Case: Handy when you have staged changes and want a ready-to-paste message for a feature, fix, refactor, or breaking change.

Quick Start

Ask the skill to write a commit message for your staged changes, and it will return a paste-ready Conventional Commit with a concise subject and an optional explanatory body only when needed.

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 staged git changes?

To generate a conventional commit message from staged git changes, provide your diff or change prompt to produce a paste-ready, type-scope-summary subject with an optional explanatory body.

What is the correct format for a conventional commit subject line?

A conventional commit subject line follows a type-scope-summary structure, using an imperative mood and strict length rules to ensure consistent version-control history and automation.

When do I need to add a body to a conventional commit message?

You need to add a body to a conventional commit message only when the reason for the change, breaking change, migration, or revert context is not obvious from the subject alone.

Can I use this for breaking changes and revert commits in version control?

Yes, you can use this for breaking changes and revert commits in version control by generating terse conventional commit messages that include necessary migration or revert context in the body.

What is the best way to write terse git commit summaries for refactors?

The best way to write terse git commit summaries for refactors is to keep the subject short, imperative, and focused strictly on the change rather than the development process.

Does this conventional commit generator work without external dependencies?

Yes, this conventional commit generator works without external dependencies, applying strict formatting rules directly to your provided git diff or change description to output a ready-to-paste message.