caveman-commit

A caveman-style conventional commit message adheres to the standard format "<type>: <description>" with a terse subject limited to 50 characters. It uses types like feat, fix, task, audit, and skill, and supports an optional body with short bullet points.

The character limit for a conventional commit subject line is approximately 50 characters. This enforces a terse description alongside the required type prefix, such as feat, fix, task, audit, or skill, ensuring concise code change descriptions.

Yes, the caveman commit format preserves important git trailers like Co-Authored-By and Closes. While the subject and body are generated in a terse caveman style, these metadata trailers are retained to maintain standard software development tracking.

Yes, you can use caveman-style commit messages for small batches of changes. The format applies to single changes or small batches, generating a concise description that clearly outlines multiple code updates while remaining readable.

Supported conventional commit types for terse messages include feat, fix, task, audit, and skill. These types prefix the subject line to categorize the code change, ensuring consistent messaging across CI pipelines and code reviews.