skills.rest
echowaves
echowavesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

caveman-commit

Generate Conventional Commits with subject and optional body.

Updated Feb 12, 2021
Search Tags:#git#code review#conventional commits#breaking changes#release notes#commit message
One-click install
npx skills add https://github.com/echowaves/WiSaw.cdk --skill caveman-commit-echowaves
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/echowaves/WiSaw.cdk/tree/main/.agents/skills/caveman-commit
Command: npx skills add https://github.com/echowaves/WiSaw.cdk --skill caveman-commit-echowaves

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes noisy, verbose commit message writing by producing short, convention-compliant messages that still preserve intent and necessary rationale.

Core Features & Use Cases

  • Conventional Commits enforcement: Produces a <type>(<scope>): <summary> subject with imperative wording and a sensible length limit.
  • Body only when needed: Adds a wrapped 72-char body when the “why” is non-obvious, for breaking changes, migrations, and reverts; otherwise omits it.
  • Consistency guardrails: Avoids common bad patterns like first-person phrasing, “as requested” filler, and redundant descriptions.

Quick Start

Tell the AI “Generate a commit message for the staged changes” and paste the resulting message into your git commit command.

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

Generate a conventional commit message by providing your intent to the AI, which outputs a paste-ready message with a type, scope, and summary. You then copy this message directly into your git commit command.

What is the correct format for a conventional commit with breaking changes?▼

A conventional commit for breaking changes uses a standard type and summary, and includes a wrapped 72-character body explaining the migration or rationale. This ensures the necessary context is preserved for release notes.

How do I keep my git commit messages concise without losing important context?▼

Keep git commit messages concise by enforcing a subject length limit and omitting the body unless the rationale is non-obvious. This guards against verbose filler and redundant descriptions while preserving intent.

Can I automate conventional commit message generation for security fixes and reverts?▼

Yes, you can automate commit message generation for security fixes and reverts by converting your intent into a convention-compliant format. The output applies consistent tone and structure for these specific scenarios.

Does conventional commit message generation work without external dependencies?▼

Yes, conventional commit message generation works without external dependencies. The process converts user intent directly into a strict subject-and-optional-body format without requiring additional packages or modules.

Related Skills

Explore More Software Engineering Skills→
aadorianaadorian

commit

Create a repository-compliant git commit message for staged or unstaged changes.

Community
Intermediate
ThedouglerThedougler

git-commit

Generate conventional git commit messages with automated file staging.

Community
Intermediate
sunny0826sunny0826
3

release-notes

Categorize Git commit logs into structured release notes in Markdown.

Community
Intermediate
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic