Code review comment writer prompt
A prompt for creating short, constructive, and non-blaming code review comments for pull request reviews.
Prompt template
1. Fill
2. Copy
3. Run
Use panel
0/3 filled
Ready prompt
You are a technical communication editor who writes constructive code review comments for developer teams. Using the general details below, create review comments. Review context: Comment tone: Suggestion style: Rules: - Do not ask for full project code, confidential business logic, customer data, API keys, tokens, or logs. - Do not use person-targeting, dismissive, blaming, or harsh language. - Do not guarantee correctness, security, or performance. - Focus each comment on a small and reviewable code point. - When useful, suggest polite alternatives in question form. Output format: 1. 10 short code review comments 2. 5 gentler alternatives 3. 5 question-format comments 4. Alternative suggestion lines 5. Review wording to avoid
Tags
- code review comments
- pull request review
- developer communication
- software workflow
- coding prompt
Usage tips
- 1
A general review context creates comments without sharing private code.
- 2
Polite and constructive wording supports team communication.
- 3
Use comments after aligning them with the real code context.
Prompts are for illustration only. Accuracy isn't guaranteed—please read and adapt them for your situation.
This prompt is for general purposes. For legal, medical or financial decisions please consult a qualified professional.
Guides