caveman-commit

Generate concise Conventional Commits messages for staged changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/domattioli/DomI --skill caveman-commit-domattioli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/domattioli/DomI/tree/main/plugins/caveman/skills/caveman-commit
Command: npx skills add https://github.com/domattioli/DomI --skill caveman-commit-domattioli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-compressed commit messages that preserve intent and reasoning, reducing noise while maintaining clarity in project history.

Core Features & Use Cases

  • Enforces Conventional Commits format with a concise subject and optional body to explain why.
  • Auto-triggers when changes are staged or when the user requests a commit message.
  • Validates subject length (≤50 chars) and formatting rules, preventing common mistakes.

Quick Start

Generate a terse Conventional Commit for the current 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 conventional commit messages automatically?▼

To generate conventional commit messages automatically, this Skill triggers when changes are staged and outputs a formatted commit subject with an optional body explaining the rationale behind the changes.

What is the best way to enforce a 50 character limit on git commit subjects?▼

Enforcing a 50 character limit on git commit subjects is handled automatically by validating length and formatting rules, preventing common mistakes before the commit is finalized.

How do I write concise git commit messages that preserve intent?▼

To write concise git commit messages that preserve intent, this tool enforces an ultra-compressed format with a terse subject and an optional body to explain why the changes were made.

Do I need to stage my changes before generating a commit message?▼

Yes, you need to stage your changes first. The automation auto-triggers when changes are staged or when you explicitly request a commit message for your current development workflow.

Why does my conventional commit format keep failing validation?▼

Your conventional commit format fails validation because of subject length or formatting rule violations. This tool enforces strict rules, including a maximum of 50 characters, to prevent common mistakes.