Conventional Commit Message Generator — ChatGPT & Claude.ai prompt
Turns a git diff or a plain description of your changes into a commit message that follows the Conventional Commits spec. Handy when you can't be bothered to recall the format.
Open on GitHubWhat Conventional Commit Message Generator does
The prompt casts the model as a commit message generator. You paste git diff output or just describe what you changed, and it returns a line shaped like <type>[optional scope]: <description>, with an optional body and footers.
The type list is fixed: feat, fix, docs, style, refactor, test, chore, ci, perf, build. A scope in parentheses goes in when it fits. Breaking changes get a ! after the type or scope, or a BREAKING CHANGE: footer. The description stays imperative, lowercase, no trailing period. The body covers what and why, not how.
Output is the commit message alone, no markdown fences, so you can copy it straight into the terminal. There is nothing to install — this is a chat prompt, not a plugin or a skill.
What it helps with
- build a Conventional Commits message from
git diffoutput - pick the right type for a CI config tweak
- mark a breaking change with
!and aBREAKING CHANGE:footer - attach an issue reference through a
Refs:footer - rewrite a vague change note in imperative mood
Example prompts for the agent
- Generate a Conventional Commits message for this diff: <paste git diff>
- Here's what I changed: added pagination to the orders list and fixed the tests. Write the commit
- This is a breaking change in the auth API, format the commit properly
How to install Conventional Commit Message Generator
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Conventional Commit Message Generator
How do I install Conventional Commit Message Generator in Claude?
You don't — it's a prompt, not an extension. Paste the text into the chat or save it as a snippet and drop it in before your change description.
What does Conventional Commit Message Generator do?
It takes a git diff or a description of your edits and returns a finished commit line following the Conventional Commits spec, with a body and footers when needed.
Which commit types does it use?
feat, fix, docs, style, refactor, test, chore, ci, perf, build. A scope in parentheses is added when relevant.
Source text
prompts.csv · CC0-1.0
I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "I need help generating a commit message for my recent changes".
© jeff-nasseri · CC0-1.0 · f/prompts.chat
