Commit Message Generator
Build a Conventional Commit from type, scope, description, body, footers and issue references.
What is Commit Generator?
A commit message builder. It assembles the header, the blank line, the body and the footers in the order the Conventional Commits spec defines, so the message parses correctly everywhere it is read.
How it works
Each field maps to one part of the message: type and scope become `type(scope):`, the checkbox adds the `!` marker, the breaking-change explanation becomes a `BREAKING CHANGE:` footer, and the issue fields become `Closes:` and `Refs:` footers. The same validation as the linter runs on the way out, so a generated message cannot be subtly malformed — a trailing period is removed and reported.
- Paste or fill in the input. Drop in a commit message, a diff, a package.json, a path list or a set of options. The tool reads it locally — nothing is uploaded and no repository is contacted.
- Adjust the rules to match your project. Every linter here takes its convention from a setting you can change: allowed commit types, header length, target branch length, known branch names. Set them once to what your team actually uses.
- Copy the result. Generated files copy straight to the clipboard or download as a real file with the right name (.gitignore, CODEOWNERS, LICENSE, COMMIT_EDITMSG), and Reset returns every field to its default.
Examples
A commit message that fails CI
"Updated(auth): Fixed the expired-token redirect." is rejected by release automation and reported here with the exact reasons: unknown type, capitalised description, past tense and a trailing period.
A .gitignore that only half works
The Checker shows which rule decides a path — and why `!keep.txt` inside an ignored directory never fires, the mistake that sends people to Stack Overflow.
A dependency bump nobody reviewed
The package.json Diff separates added, removed and changed entries per section, so a caret bump of a runtime dependency does not hide inside a lockfile-sized pull request.
A diff pasted from a code review comment
The Diff Viewer understands several `diff --git` blocks, mode-only changes, renames and binary stubs, and calls out a pasted `--stat` summary instead of rendering an empty box.
Common mistakes
Committing a .gitignore without checking it
Rules look right and behave differently: a pattern containing a slash is anchored to the root, a trailing slash means directories only, and a file inside an ignored directory cannot be re-included. Check the paths that matter before you commit the file.
Rewriting published history
A clean commit history is worth having, but amend, rebase and filter-repo change commit hashes. Only rewrite commits that nobody has pulled; after a rewrite, push with --force-with-lease rather than --force.
Treating a generated file as if it were reviewed
These tools produce a starting point, not a decision. Check the licence text against the canonical source, read the security policy before publishing it, and make sure a CODEOWNERS team actually exists — GitHub silently ignores rules whose owner has no write access.
Putting slow checks in a pre-commit hook
A hook that takes 30 seconds gets bypassed with --no-verify within a week, and then it protects nothing. Keep pre-commit to formatting and linting, move type checks and tests to pre-push or CI.
Frequently asked questions
Why does the generated file use the name COMMIT_EDITMSG?
Because that is the file git itself writes your message into, so you can drop the download straight into place or commit it with git commit -F COMMIT_EDITMSG. It avoids the shell quoting that mangles multi-line messages.
Should I always fill in the body?
Not always, but a body is where the reasoning goes — what the change is for, what you rejected, what reviewers should watch. The diff already shows the what.
How do I reference an issue without closing it?
Put it in the References field. `Closes #12` (or `Fixes #12`) closes the issue when the commit lands on the default branch; `Refs: #12` just links it.