skills.rest
storm-software
storm-softwareOFFICIAL
Explore all skills by this author →
Website𝕏@StormSoftwareHQGitHub

caveman-commit

Generate conventional commit messages for staged Git changes.

2|1|Updated Dec 16, 2025
Search Tags:#automation#git#commit#generate#message#conventional
One-click install
npx skills add https://github.com/storm-software/shell-shock --skill caveman-commit-storm-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/storm-software/shell-shock/tree/main/.agents/skills/caveman-commit
Command: npx skills add https://github.com/storm-software/shell-shock --skill caveman-commit-storm-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers waste time drafting commit messages that are either too verbose or not following the Conventional Commits format. This skill automates creation of concise, convention‑compliant messages, ensuring clarity and consistency.

Core Features & Use Cases

  • Enforces Conventional Commit format with correct type, optional scope, and imperative subject.
  • Limits subject length to ≤50 characters and wraps body at 72 characters.
  • Provides auto‑trigger when changes are staged, ideal for quick commits during development.
  • Use case: A developer typing “/caveman-commit” or “write a commit” receives a ready‑to‑paste commit message respecting project conventions.

Quick Start

Ask the skill to generate a commit message for your staged changes.

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 changes, you trigger the generation process to produce a convention-compliant message with a correct type, optional scope, and imperative subject.

What is the character limit for a conventional commit subject and body?▼

A conventional commit subject is limited to 50 characters or fewer, while the optional body is wrapped at 72 characters to ensure concise and readable formatting.

How do I write a conventional commit message without running git commands?▼

You can write a conventional commit message without running git commands by analyzing the staged code changes and applying formatting rules to output a ready-to-paste message.

Does the conventional commit generator work with all git workflows?▼

The conventional commit generator works with Git workflows where developers need conventional-commit-style messages, providing auto-trigger functionality when code changes are staged.

Why do my generated commit messages fail conventional commit formatting rules?▼

Generated commit messages fail conventional commit formatting rules if they lack the correct type, optional scope, imperative subject, or exceed the 50-character subject limit.

Can I use caveman-commit to automate commit message creation during development?▼

You can use caveman-commit to automate commit message creation during development by triggering it to generate ready-to-paste, convention-compliant messages for your staged changes.

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
notquenotque
415

git-commit-flow

Automate phase-gated git commit workflows with validation, staging, and CLAUDE.md compliance.

Community
Advanced
michaelvolzmichaelvolz

rm-commit

Create repo-specific conventional commit payloads from the working tree.

Community
Intermediate