caveman-commit

To generate conventional commit messages for breaking changes, request a commit message and the assistant outputs a terse subject with an optional body explaining the non-obvious intent or specific details like security fixes and data migrations required for the breaking change.

The correct format for a conventional commit subject line is <type>(<scope>): <imperative summary>. The subject must use imperative mood, adhere to length caps, and avoid fluff or non-standard narrative text to keep histories readable.

To write git commit messages in imperative mood, prompt the assistant for a commit message. It enforces the imperative mood in the subject summary and outputs only the clean message, forbidding AI attribution and narrative text.

You should include a body in a conventional commit only when the reasoning is non-obvious or when detailing breaking changes, security fixes, data migrations, or reverts. It preserves necessary context for future reviewers without adding noisy fluff.

No, this commit message generator does not stage changes or run git commit. It outputs only the copy-ready conventional commit message text, which you can then paste directly into your existing developer workflow.