caveman-commit

Generate conventional commit messages for staged git changes by processing your repository diff to produce terse subject lines with optional bodies, preserving intent while enforcing length limits and allowed types.

The conventional commits format compresses message noise by enforcing a terse subject line structure of type(scope): imperative summary, adding an optional body only when the reasoning behind changes is not obvious.

You can enforce subject length limits and specific allowed commit types in automated git commits by applying the caveman-commit Skill to validate and generate constrained conventional commit messages.

Add a body or breaking change reference to a conventional commit when the reasoning for the change is not obvious, or when you need to document issue mentions and breaking changes for team workflows.

This conventional commit generator works without extra dependencies, allowing you to directly process staged changes and apply consistent messaging across software projects without additional environment setup.