skills.rest
austinwilcox
austinwilcoxCOMMUNITY
Explore all skills by this author →
Website𝕏@Seconds21iveGitHub

caveman-commit

Generate terse Conventional Commit messages with imperative subjects and optional bodies.

1|1|Updated Jul 31, 2023
Search Tags:#git#developer workflow#conventional commits#staging#semantic formatting#commit message generation
One-click install
npx skills add https://github.com/austinwilcox/dotfiles --skill caveman-commit-austinwilcox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/austinwilcox/dotfiles/tree/main/.claude/skills/caveman-commit
Command: npx skills add https://github.com/austinwilcox/dotfiles --skill caveman-commit-austinwilcox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes “noise” from commit messages by producing concise, standardized Conventional Commits that preserve intent and only adds a body when the why is genuinely unclear.

Core Features & Use Cases

  • Ultra-compressed subject lines: Produces an imperative, conventional <type>(<scope>): <summary> subject that stays short and readable.
  • Body only when needed: Adds a wrapped 72-column body exclusively for non-obvious reasoning, breaking changes, migrations, and relevant references.
  • Rule-consistent output: Avoids fluff, AI attribution, emojis, and common restatements; outputs a copy-ready message in a code block.

Example use case: you stage changes and want a commit message that correctly follows feat/fix/... conventions while explaining the “why” only when the diff isn’t self-explanatory.

Quick Start

When you say “write a commit” or invoke caveman-commit, tell it what you changed (or rely on the staged changes trigger) and paste the resulting commit message.

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

To generate conventional commit messages for staged git changes, use a tool that outputs an imperative `<type>(<scope>): <summary>` subject targeting 50 characters, adding a wrapped 72-column body only when the reasoning is non-obvious.

What is the best way to format git commit messages to remove unnecessary phrasing?▼

Formatting git commit messages to remove unnecessary phrasing involves producing terse Conventional Commits that preserve intent, avoiding fluff, AI attribution, and emojis while outputting a paste-ready code block.

How do I write a conventional commit subject line that stays under 50 characters?▼

Writing a conventional commit subject line under 50 characters requires an imperative `<type>(<scope>): <imperative summary>` format that stays short and readable while strictly avoiding common restatements.

When should I add a body to a conventional commit message?▼

Add a body to a conventional commit message only when the "why" is non-obvious or for breaking changes, security notes, and migrations, keeping wrapped text lines at 72 characters.

Does conventional commit formatting work without adding emojis or AI attribution to the message?▼

Conventional commit formatting works without adding emojis or AI attribution by applying rule-consistent output that avoids fluff and restatements, producing a clean, copy-ready message in a code block.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
biwakonbubiwakonbu

git-commit

Stage changes and generate descriptive Git commit messages automatically.

Community
Basic
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate