---
name: address-pull-request-review-comments
description: "Works through every review comment on a pull request, applies the changes you agree with, and replies to each thread so nothing is left hanging. Use when a pull request has received review comments and the author needs each one fixed, answered, or politely contested with a reply on every thread. Do not use for performing a review on someone else's code. Related topics: coding, communication."
---

# Address Pull Request Review Comments

Works through every review comment on a pull request, applies the changes you agree with, and replies to each thread so nothing is left hanging.

## When to use

Use this skill when a pull request has received review comments and the author needs each one fixed, answered, or politely contested with a reply on every thread. Do not use it for performing a review on 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. List every review comment in a numbered table and classify it as Fix, Discuss, Question, or Nit.
3. Apply the smallest change that satisfies each Fix item while keeping to the intent of the PR.
4. Draft reasoned replies for disagreements and short answers for questions.
5. Run the tests after the changes when enabled and report the outcome.
6. Write one reply per thread and report threads resolved against threads still open.

## Inputs

- **Pull request** (free text, e.g. "Link or number")
- **Review comments** (longer free text)
- **Intent of the PR** (longer free text)
- **Comments I disagree with** (longer free text)
- **Reply tone** (choose one: Brief, Friendly, Formal)
- **Run tests after changes** (choose one: Yes, No)

## Output

A numbered comment table with classification and action, the code changes made, one drafted reply per thread, and a resolved-versus-open count.

## Prompt template

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

### Address Pull Request Review Comments

Handle the review feedback on my pull request.

- Pull request: {{Pull request}}
- Review comments: {{Review comments}}
- Intent of the PR: {{Intent of the PR}}
- Comments I disagree with: {{Comments I disagree with}}
- Reply tone: {{Reply tone}}
- Run tests after changes: {{Run tests after changes}}

List every comment in a numbered table and classify each as Fix, Discuss, Question, or Nit. Do not skip any. For Fix items, make the smallest change that satisfies the reviewer, keeping to the intent of the PR. For comments I disagree with, draft a respectful reply that gives the reason and offers an alternative instead of changing code. For Questions, answer with a short explanation and a code reference. Group related comments so one change closes several threads. When tests are enabled, run them after the changes and report the result. Write one reply per thread saying what changed, with the commit hash if known, or why not. Finish with a count of threads resolved against threads still open.

## Pitfalls

- Skipping nits silently, which leaves threads that the reviewer must chase.
- Changing code the reviewer did not mention while fixing a comment.
- Replying 'done' without saying what changed.