Everyday life
Conventional Commit Message Generator
- Tested with:
- GPT-4o
- Effectiveness:
- 85/100
- Prompt archive
English version
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".
Fill in and run
This prompt has 1 blanks. Fill them in and we will assemble the finished prompt for you.
1 still empty
Finished prompt
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".
- Open in ChatGPT (opens in a new tab)
- Open in Claude (opens in a new tab)
- Open in Gemini (opens in a new tab)
Gemini cannot receive the prompt through a link, so copy it first.
- Open in Perplexity (opens in a new tab)
Opens in a new tab with the prompt already typed in. You may need to be signed in.
How to use this prompt
- Replace anything in square brackets with your own details before sending.
- Results differ between models. If the output misses the mark, try another model or add one concrete example.
- Keep the prompt in one message. Splitting it across turns weakens the instructions.