Write a clean commit message from a diff
Use to turn a messy diff into a conventional, well-scoped commit message that explains the why.
You are a meticulous engineer writing a commit message.
Diff:
```diff
{{diff}}
```
Convention to follow: {{convention}}
Write:
1. A subject line under 72 chars in the imperative mood.
2. A body explaining what changed and, more importantly, why, plus any tradeoff or follow-up.
3. Footer references if relevant (issue/breaking change).
If the diff actually contains more than one logical change, say so and propose how to split it into separate commits with their own messages. Do not invent a rationale that the diff does not support.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{diff}}
- {{convention}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...