caveman-commit

Generate Conventional Commits with type(scope) and imperative subjects.

4|2|Updated May 18, 2022

Search Tags:#git #commit #formatting #generate #commit-message #conventional-commits

Ready to run

npx skills add https://github.com/pjmagee/starwars-data --skill caveman-commit-pjmagee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/pjmagee/starwars-data/tree/main/.agents/skills/caveman-commit
Command: npx skills add https://github.com/pjmagee/starwars-data --skill caveman-commit-pjmagee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill compresses verbose commit messages into concise Conventional Commits that preserve intent and reasoning while removing noise, making changelogs and git history clearer and easier to review.

Core Features & Use Cases

Strict Conventional Commits: Produces messages in type(scope): imperative subject format and enforces imperative mood and capitalization conventions.
Minimal, contextful bodies: Omits the body unless the reasoning is non-obvious, required for breaking changes, migrations, or linked issues; wraps at 72 characters.
Use Case: Invoke when staging changes, in editor/assistant prompts like "write a commit", or via auto-trigger to generate a paste-ready commit message that follows team conventions.

Quick Start

Generate a terse Conventional Commit for the staged changes, including a body only when the reason is not obvious.

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

To generate a conventional commit message for staged git changes, invoke the Skill with a prompt like "write a commit" to produce a paste-ready message formatted as type(scope): imperative subject, preserving intent while removing noise.

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

The correct format for a conventional commit subject line is type(scope): imperative subject. The subject should use imperative mood, be capitalized, and stay under a 50-character preferred limit with a hard cap of 72 characters.

When should I include a body in a conventional commit message?▼

You should include a body in a conventional commit message only when the reasoning is non-obvious, such as for breaking changes, migrations, or linked issues. The body must wrap at 72 characters and omit personal pronouns or AI attribution.

Does the conventional commit generator work with editor integrations?▼

Yes, the conventional commit generator works with editor integrations and assistant prompts. You can trigger it automatically or manually when staging changes to output concise commit messages that follow team conventions without requiring external dependencies.

Why should I use an ultra-compact commit message format instead of verbose git logs?▼

An ultra-compact commit message format removes noise from verbose descriptions while preserving intent and reasoning. This makes git history clearer and changelogs easier to review by enforcing strict conventional commits with minimal, contextful bodies.