TechnicalCollectible prompt
Git commit message from a diff
Write a Git commit message for this diff:
{{git_diff}}
Convention to follow: {{commit_convention}} (for example Conventional Commits, or a plain imperative subject)
Context the diff doesn't show: {{reason_for_change}}
Rules:
- A subject line in the imperative mood, ideally 50 characters or fewer and never over 72
- A blank line, then a body wrapped at 72 characters that explains what changed and why, not a file-by-file list
- Call out breaking changes, migrations, and configuration changes explicitly
- Reference issue numbers only if I provided them
Return the message in a plain text block. If the diff mixes unrelated changes, say so, suggest how to split it into separate commits, and write a message for each.
Technicalnvoka.com/library/nvoka-git-commit-message-from-diffScan to open
Technical
Git commit message from a diff
Write a clear commit message that explains what changed and why.
Curated by Nvoka
GitHub CopilotClaude CodeCursorChatGPT
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 3 filledYour prompt
Write a Git commit message for this diff:
{{git_diff}}
Convention to follow: {{commit_convention}} (for example Conventional Commits, or a plain imperative subject)
Context the diff doesn't show: {{reason_for_change}}
Rules:
- A subject line in the imperative mood, ideally 50 characters or fewer and never over 72
- A blank line, then a body wrapped at 72 characters that explains what changed and why, not a file-by-file list
- Call out breaking changes, migrations, and configuration changes explicitly
- Reference issue numbers only if I provided them
Return the message in a plain text block. If the diff mixes unrelated changes, say so, suggest how to split it into separate commits, and write a message for each.
