Commit Message Suggester (from git diff)
Draft a commit message from your staged changes: type, scope and a list of files with line counts.
Use the tool
Why this tool exists
The tool reads git diff headers and hunks, counts additions and deletions per file, classifies files (tests, docs, CI, build files, styles, code) and chooses a type: test, docs, ci, build, style, fix, feat or refactor. The scope comes from the common directory of changed code files.
It is a rule-based starting point. Replace the subject with what the change does and why, add "!" or a BREAKING CHANGE footer for incompatible changes, and keep the subject under about 72 characters.
No data is sent anywhere: the work happens in your browser, so you can use it offline once the page has loaded.
How to use it
- Run git diff --staged (or git diff) and copy the output.
- Paste it and read the suggested subject and file list.
- Rewrite the subject to say what and why.
- Commit with git commit -m.
Frequently asked questions
Does it understand my code?
No. It looks at file paths, change sizes and a few keywords. Review the type it picks.
What are Conventional Commits?
A convention of "type(scope): subject" messages that tools can use to build changelogs and version numbers.
Is my diff sent anywhere?
No. It stays in the page.
Is my data sent anywhere?
No. Everything is processed in your browser, and the page makes no network requests with your input.