resolve-pr-feedbacklisted

# Resolve PR Feedback > **Load this skill the moment a review arrives — before reading the comments, not after fixing > them.** The trigger is a review landing on a PR you opened, however it is phrased ("reviewed", > "minor review landed", "see my comments"), and it fires even when the fixes look obvious. > > Skipping it does not make you get the _fixes_ wrong — it makes you skip the parts that are not > fixes. Both halves of Phase 5 were missed the last time this happened, on `service-genai#21`: > > - **[§5.1](#51-reply-on-every-addressed-thread)** — replies went out with bare `gh`, attributing > the agent's analysis to the human whose token ran it. Unrecoverable once the human decides a > re-post is not worth it. > - **[§5.2](#52-resolve-settled-threads)** — nothing was resolved, leaving the reviewer to walk > seven answered threads by hand. > > Reply and resolve are one action, not a fix followed by paperwork. This skill governs how Claude surveys a pull request's state and works through reviewer feedback. It runs as a passive read ("check PR 532") and as an active workflow ("address the comments on PR 532"). Both modes share Phase 1; only the resolve workflow continues through Phases 2–5. It **also** governs discussion under an **issue** — chiefly the planning issues `plan-feature` produces, where the human and the agent converse in comments while the body holds the agreed plan. Phases 1–5 are written for PRs. When the work is an issue, start at [Issue discussion