Reply to code review comments I disagree with
Drafts calm, evidence-based replies to review feedback so you can resolve disagreements without stalling the pull request.
The prompt
Help me respond to code review comments I disagree with.
The code in question: [PASTE THE DIFF OR SNIPPET]
Reviewer's comments: [PASTE EACH COMMENT]
Why I wrote it this way: [MY REASONING, CONSTRAINTS, CONTEXT THEY MAY NOT HAVE]
Relationship: [e.g. "senior teammate", "owner of this module", "peer on another team"]
How much it matters to me: [hill to die on / prefer my way / happy to change]
For each comment:
1. Steelman the reviewer: what concern might they have that I'm missing? Say honestly if they have a point.
2. Classify it: correctness, maintainability, style/preference, or scope creep.
3. Recommend: accept, accept with a tweak, push back, or defer to a follow-up ticket.
4. Draft the reply (2-5 sentences): acknowledge their concern, give my reasoning with concrete evidence (benchmarks, docs, existing conventions), and propose a way to resolve it.
Rules:
- No sarcasm, no "as I said", no appeals to seniority.
- Concede quickly on style points unless they break a team convention.
- If we're likely going in circles, suggest a 10-minute call or a team decision and draft that message.
Return a table (comment, classification, recommendation) followed by the drafted replies.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- PASTE THE DIFF OR SNIPPET
- PASTE EACH COMMENT
- MY REASONING, CONSTRAINTS, CONTEXT THEY MAY NOT HAVE
- hill to die on / prefer my way / happy to change
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Design consistent API error responses developers can act onTurns unhelpful API errors into a consistent format with clear codes, statuses, and messages that tell callers exactly what to fix.
- Review AI-generated code before I merge itChecks code written by an AI assistant for the specific mistakes these tools make: invented APIs, shallow tests, and hidden security gaps.
- Diagnose slow launches and API cold starts in my mobile appA codebase-specific diagnosis of startup time, serverless cold starts, and network waste, with fixes ranked by impact on perceived speed.
- Set up experiment tracking for a machine learning training runStep-by-step setup to log metrics, hyperparameters, and artifacts from your training script, locally or on a cluster.