caveman-commit

Enforce Conventional Commits format with subject length limits and scope.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/venomez-viper/PathWise --skill caveman-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-commit
Source: https://github.com/venomez-viper/PathWise/tree/main/.agents/skills/caveman-commit
Command: npx skills add https://github.com/venomez-viper/PathWise --skill caveman-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduce commit-message noise while preserving intent by enforcing the Conventional Commits format.

Core Features & Use Cases

  • Subject length enforcement: enforces ≤50 chars for the subject and ≤72 chars wrapped body when needed.
  • Structured format: supports types (feat, fix, refactor, etc.) and optional scope, with proper capitalization after the colon.
  • Guidance and examples: provides rules and examples to improve consistency across teams.

Quick Start

Generate a terse, conventional-commits compliant commit message for this change.

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?

Generate conventional commit messages by enforcing subject length limits of 50 characters, structured types like feat or fix, optional scope, and body guidance explaining the 'why' to reduce commit noise while preserving intent.

What is the character limit for conventional commit subjects?

The character limit for conventional commit subjects is 50 characters, with wrapped body content extending up to 72 characters when needed. This enforces terse, readable Git history while standardizing development workflows.

Does this commit message generator support breaking changes notation?

Yes, this commit message generator supports breaking changes notation. It provides specific rules and examples for handling breaking changes within the Conventional Commits format to improve consistency across software development teams.

How do I format a conventional commit body to explain why a change was made?

Format a conventional commit body by focusing on the 'why' behind the code change rather than the 'what'. The generator provides body guidance to ensure the wrapped text stays under 72 characters and preserves development intent.

What are the limitations of enforcing strict conventional commit formats?

Limitations of enforcing strict conventional commit formats include constraining subjects to 50 characters and requiring specific types like feat or fix. If a code change does not fit standard types, structuring the commit message becomes difficult.