address-reviewlisted

# address-review Work through the review comments on an open PR and resolve them **deliberately**. Reviewers — and especially bots — are high-recall, low-precision: a large share of their comments are false positives, style nits, or misreadings of the contract. Blindly "fixing everything a reviewer said" is net-negative. The job of this skill is to **triage first, challenge each comment, then act** — fixing what's real, refuting what isn't (with rationale), and deferring what's out of scope. This is standalone and **manually invoked** — it isn't bound to a pipeline stage. But it inherits the kit's conventions: the frozen contract is authoritative, sensitive areas (canonical list in the project's `AGENTS.md` → Sensitive areas) get extra care, comments cite the durable doc (ADR/PRD/contract) not the pipeline, and outward-facing actions and merges stay the human's call. It is **not** a second `code-review`. `code-review` proactively audits your own diff before you push; this skill reactively triages what *reviewers* already said on an open PR. If a comment prompts a broader re-audit, that's `code-review`'s job — route back to it. ## Steps 1. **Identify the PR — infer, don't interrogate.** Resolve it from the current branch (`gh pr view` with no number returns the open PR for the checked-out branch), so right after you've landed a task the skill already knows which PR this is — state it and move on. Only ask the user when there's no PR for the branch or several plau