Verified:GitHub

caveman-commit

Generates formatted commit messages with optional explanatory body text.

199|41|Updated Oct 25, 2020

Search Tags:#git workflow #conventional commits #breaking changes #release notes #developer productivity #commit message #imperative subject

Ready to run

npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill caveman-commit-rvdbreemen

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of noisy, inconsistent commit messages by generating terse Conventional Commits that preserve intent and necessary context for future reviewers.

Core Features & Use Cases

Conventional Commit formatting: Produces a subject in the required <type>(<scope>): <imperative summary> pattern with length caps to keep histories readable.
Context-aware body generation: Adds a body only when the “why” is non-obvious or when breaking changes, security fixes, data migrations, or reverts require extra detail.
Copy-ready output: Outputs only the commit message (no staging, no git commit, no amending), ready to paste into your workflow.

Quick Start

Ask for a commit message by saying: generate a commit message for adding a new OAuth token refresh endpoint and explain the reason briefly.

Frequently Asked Questions about caveman-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate conventional commit messages for breaking changes?▼

To generate conventional commit messages for breaking changes, request a commit message and the assistant outputs a terse subject with an optional body explaining the non-obvious intent or specific details like security fixes and data migrations required for the breaking change.

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

The correct format for a conventional commit subject line is <type>(<scope>): <imperative summary>. The subject must use imperative mood, adhere to length caps, and avoid fluff or non-standard narrative text to keep histories readable.

How do I write git commit messages in imperative mood?▼

To write git commit messages in imperative mood, prompt the assistant for a commit message. It enforces the imperative mood in the subject summary and outputs only the clean message, forbidding AI attribution and narrative text.

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

You should include a body in a conventional commit only when the reasoning is non-obvious or when detailing breaking changes, security fixes, data migrations, or reverts. It preserves necessary context for future reviewers without adding noisy fluff.

Does this commit message generator run git commit or stage changes automatically?▼

No, this commit message generator does not stage changes or run git commit. It outputs only the copy-ready conventional commit message text, which you can then paste directly into your existing developer workflow.