caveman-commit

Generate conventional commit messages from staged code changes.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/achmf/KostaHub --skill caveman-commit-achmf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/achmf/KostaHub/tree/main/.agents/skills/caveman-commit
Command: npx skills add https://github.com/achmf/KostaHub --skill caveman-commit-achmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates verbose, noisy, and redundant commit messages by enforcing a strict, intent-focused format that prioritizes the why over the what.

Core Features & Use Cases

  • Conventional Commits Enforcement: Automatically structures messages using standard types like feat, fix, and refactor.
  • Noise Reduction: Strips away fluff and AI-generated attribution, focusing on the reasoning behind changes.
  • Use Case: When you have finished a complex refactor and need a concise, professional commit message that explains the architectural reasoning without restating the obvious diff.

Quick Start

Ask the caveman-commit skill to generate a commit message 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 concise conventional commit messages for staged git changes?

To generate concise conventional commit messages, you analyze staged git changes for intent and reasoning, applying imperative mood and a 72-character line limit. This strips away fluff to focus on the why behind the architectural modifications.

Why do my automated conventional commits include unnecessary AI attribution and fluff?

Automated conventional commits include unnecessary AI attribution and fluff because standard generators often restate the obvious diff rather than focusing on the reasoning. Intent-focused message generation eliminates this noise by enforcing a strict format prioritizing the why over the what.

Can I enforce a 72-character line limit and imperative mood for conventional commit messages?

Yes, you can enforce a 72-character line limit and imperative mood for conventional commit messages by applying strict intent-focused formatting rules. This standardizes your git history into high-signal entries that explicitly document breaking changes and non-obvious logic.

What is the best way to document breaking changes in conventional commits?

The best way to document breaking changes in conventional commits is to explicitly state them within an intent-focused, ultra-compressed message. This approach ensures the architectural reasoning is highlighted without restating the obvious code diff.

Does intent-focused commit generation work for complex refactors without restating the diff?

Yes, intent-focused commit generation works for complex refactors by analyzing the staged code changes to extract reasoning rather than restating the diff. It produces a concise, professional commit message that explains the architectural decisions.