review-prlisted

Take a reviewed draft PR to production. **This body is self-sufficient — run it without reading anything else.** Every command the landing needs is here. The pointers name where an argument or a piece of evidence lives, for when a step surprises you: `docs/agents/workflow.md` is the standing policy, `docs/agents/issue-tracker.md` and `docs/agents/triage-labels.md` the tracker's, `docs/infrastructure.md` the register of what is provisioned, and `docs/incidents.md` the observation behind any rule that has one. Solo, "mark ready" signals nobody and GitHub simply refuses to merge a draft, so it is a step on the way rather than the destination. This skill is the landing. **A code review should already have covered this branch's range.** `/implement`'s own review satisfies that when it ran against the committed change. Do not send the user back for a second pass over a range that has already been reviewed. Stop only when no review covered it: `/implement` never ran, the diff it read was empty or partial, or commits have landed since. A review of an empty range reports no findings and reads like a clean one, so the question to ask is **which diff command it ran** — not whether a review happened. Ask rather than assume when this session cannot tell. (`docs/agents/workflow.md` → *The review runs once*.) **Commits landing since is the bounded case.** After two rounds, a commit that does nothing but apply the second round's own findings is disclosed rather than reviewed a third time