---
name: code-review-feedback-responder
description: "Works through every review comment on a change, choosing to accept, push back with evidence or ask, and leaves none silently ignored. Use when review comments have arrived on a change and each one needs a reasoned response or edit. Do not use for preparing a change for review or giving a review of someone else's code. Related topics: coding, communication."
---

# Code Review Feedback Responder

Works through every review comment on a change, choosing to accept, push back with evidence or ask, and leaves none silently ignored.

## When to use

Use this skill when review comments have arrived on a change and each one needs a reasoned response or edit. Do not use it for preparing a change for review or giving a review of someone else's code.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Number every comment and read each against the actual code before deciding anything.
3. Give each comment one outcome of accept, push back with evidence, or ask a precise question.
4. Group comments that one edit resolves and order the edits to make.
5. Draft a short, specific reply for each comment when drafts are requested.
6. Confirm every comment number has an outcome so none is silently dropped.

## Inputs

- **Review comments** (longer free text)
- **The change** (longer free text)
- **Project conventions** (longer free text)
- **Stance** (choose one: Accommodating, Balanced, Firm on design)
- **Draft replies** (choose one: Yes, No)

## Output

A numbered table of comment, outcome, reason and planned edit, followed by the ordered edit list and the draft replies if requested.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Code Review Feedback Responder

Go through the review comments on my change and decide how to respond to each.

- Review comments: {{Review comments}}
- The change: {{The change}}
- Project conventions: {{Project conventions}}
- Stance: {{Stance}}
- Draft replies: {{Draft replies}}

Number every comment and give each exactly one outcome. Accept: the reviewer is right, so describe the exact edit. Push back: you disagree, so state the reason with evidence from the code, a test, a convention or a measurement, and stay polite and specific. Ask: the comment is unclear or depends on context, so write one precise question. Check the suggestion against the code before accepting it, since a plausible suggestion can break a case. Group related comments so one edit resolves them. Then list the edits to make in order, and when drafts are on, write a short reply per comment. End with a check that every comment number has an outcome.

## Pitfalls

- Accepting a suggestion without testing it, which can reintroduce a bug the original code avoided.
- Pushing back with opinion instead of evidence, which turns the thread into a debate.
- Skipping a minor comment, which reads as being ignored.