caveman-commit

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.

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.

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.

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.

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.

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.