Answer code review comments clearly

Prompt that sorts review comments, decides now, later or keep for each one and drafts calm replies. Paste it into an AI tool of your choice, which then drafts the review replies.

Topic: Apps & prototypes
Type: Prompt
Level: Beginner
Time: about 10 min

Results depend on the tool, the model and what you enter.

Result preview

Example: written by our editors, not real AI output.

Fill in

What you type stays in this browser window. We store and send nothing.

ChangeWhat does your change do?

CommentsWhich comments did you get?

SituationWhat is the situation?

Your prompt

Help me answer the review comments on my change.
Change: [Change]
Comments: [Comments]
Situation: [Situation]
Approach: 1. Group the comments into bugs, design questions, style and questions of understanding. 2. For each comment, propose whether I change it now, open a follow-up ticket or keep my version, always with a short reason. 3. Write a reply for each comment in a calm, factual tone that thanks for real finds and asks back when a comment is unclear. 4. Where I keep my version, suggest how to explain it without sounding defensive. 5. List the code changes promised in the replies as a checklist. 6. Name comments where a short call would be faster than more text.
Output: table with comment, group, decision and reply draft, plus the checklist of promised changes.

Take particular care to give every decision a reason and keep the tone factual and friendly.

Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.

Help me answer the review comments on my change.
Change: [Change]
Comments: [Comments]
Situation: [Situation]
Approach: 1. Group the comments into bugs, design questions, style and questions of understanding. 2. For each comment, propose whether I change it now, open a follow-up ticket or keep my version, always with a short reason. 3. Write a reply for each comment in a calm, factual tone that thanks for real finds and asks back when a comment is unclear. 4. Where I keep my version, suggest how to explain it without sounding defensive. 5. List the code changes promised in the replies as a checklist. 6. Name comments where a short call would be faster than more text.
Output: table with comment, group, decision and reply draft, plus the checklist of promised changes.

Take particular care to give every decision a reason and keep the tone factual and friendly.

Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.

This is an instruction for an AI, not the result itself.

Where this prompt works

These AI tools are a good fit for this prompt:

How to use it

Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
Copy the finished prompt into an AI tool of your choice.
Paste the comments without the reviewers' names; the reply drafts work just as well with "Reviewer 1" and "Reviewer 2".

Why does this work?

Review threads go wrong when every comment gets the same weight. Sorting first and giving each decision a reason keeps the discussion on the code and makes approval easy.

Tips

Do not paste internal code you may not share with an AI tool; describe the change instead.

You may use our prompts freely, including at work. Please do not republish them as your own collection. We give no warranty for AI results; check them yourself. Terms of use

Answer code review comments clearly

Result preview

Fill in

Your prompt

Where this prompt works

How to use it

Why does this work?

Tips

Also a good fit

Clean up stale feature flags New

Write form error messages people understand New

Choose pagination for an API list New