caveman-commit

Generate terse Conventional Commits messages with optional scope and body.

Updated Apr 19, 2026

Search Tags:#automation #git #commit #style-guide #conventional-commits #subject-length

Ready to run

npx skills add https://github.com/NihaalManaf/LDR-Island --skill caveman-commit-nihaalmanaf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/NihaalManaf/LDR-Island/tree/main/.agents/skills/caveman-commit
Command: npx skills add https://github.com/NihaalManaf/LDR-Island --skill caveman-commit-nihaalmanaf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-compact commit messages trim noise while preserving intent, enforcing the Conventional Commits format for clean, navigable history.

Core Features & Use Cases

Generates concise Conventional Commits from user prompts with optional scope.
Enforces subject length ≤50 characters and standard verb mood.
Auto-body handling: includes a body only when the rationale is non-obvious.

Quick Start

Tell caveman-commit to write a commit for your latest 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 from my code changes?▼

To generate conventional commit messages automatically, describe your code changes in a prompt and the tool outputs a standardized summary. It enforces Conventional Commits types, limits subject length to 50 characters, and adds an optional body only when reasoning is non-obvious.

What is the best way to keep git commit subjects under 50 characters while following a style guide?▼

The best way to keep git commit subjects under 50 characters while adhering to a style guide is using an automated generator. It enforces the 50-character limit, applies standard verb mood, and ensures your commit history remains clean and navigable.

How do I write a conventional commit with an optional body only when necessary?▼

Writing a conventional commit with an optional body requires including the body only when the rationale is non-obvious. The generator automatically detects if the reasoning needs explanation and adds the body accordingly, otherwise producing a terse subject-only message.

Does the conventional commits format support adding a scope to ultra-compact messages?▼

Yes, the conventional commits format supports adding an optional scope to ultra-compact messages. When you prompt for a commit summary, you can include a scope to provide additional context while maintaining the terse, standardized format.

When should I not use an automated commit message generator?▼

You should not use an automated commit message generator when your changes require detailed multi-paragraph explanations or non-standard formatting. The tool is designed for ultra-compact summaries and trims noise, so complex rationale extending beyond a simple optional body may be lost.

Can I use caveman-commit to enforce subject length limits across my git repository history?▼

Yes, you can use caveman-commit to enforce subject length limits across your git repository history. It consistently generates conventional commit messages with subjects capped at 50 characters, ensuring standardized and navigable logs for every change you describe.