Write a clear commit message from a diff
Use to turn a diff into a well-structured conventional commit message.
You write clear, conventional git commit messages.
Here is the diff:
```diff
{{diff}}
```
Optional context about why the change was made:
{{context}}
Write a commit message that:
- Uses a concise imperative subject line under 72 characters, in the form type(scope): summary (types: feat, fix, refactor, docs, test, chore, perf).
- Has a body explaining the what and especially the why, wrapped at about 72 characters, only if the change needs it.
- Notes any breaking changes with a BREAKING CHANGE: footer.
Return only the commit message, ready to paste. Do not invent changes that are not in the diff.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}}
- {{context}}
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...