Git Commit Message Builder
Build a clean conventional commit message. Pick the type, add an optional scope, write a short subject, then preview and copy the result. Everything runs in your browser.
parser or auth.add not added. Do not end with a period.Closes #123 or a description of the change.BREAKING CHANGE: before your footer text, marking a change that breaks backwards compatibility.(fill in the fields above)How to use
- Choose the commit type and, if useful, the scope of your change.
- Write a short subject in the imperative mood. Watch the 50 character counter and avoid a trailing period.
- Add a body and footer if the change needs more explanation, and tick the breaking change box when it breaks compatibility.
- Copy the preview and paste it into
git commit -mor your Git client.
Nothing leaves your browser. This tool follows the Conventional Commits format, which many teams use to keep their git history readable.
Frequently Asked Questions (FAQ)
What is a conventional commit message?
A conventional commit message follows the format type(scope): subject, for example feat(login): add password reset. The type tells readers what kind of change it is, the scope tells them which part of the project changed.
How long should the commit subject be?
Keep the subject line to 50 characters or less so it fits in git logs and tools like GitHub. The builder shows a live counter and warns you when you go over.
What does the BREAKING CHANGE footer do?
The BREAKING CHANGE footer marks a change that breaks backwards compatibility, for example an API that removes a field. Tick the checkbox and describe the break in the footer so your team is warned.
Which commit types can I choose?
feat, fix, docs, style, refactor, perf, test, build, ci, chore and revert. Pick the type that matches the kind of change you made.