pr-resolvelisted

# /gku:pr-resolve — act on the comments on your pull request Someone (usually the automated reviewer, sometimes a colleague) left comments. This works through all of them in one pass, without touching whatever you currently have checked out. This is the one skill here that **writes code and pushes**. It only ever works on **your own** pull request. **The rule that matters: never fix blindly.** An automated reviewer is tuned to sound confident and is regularly wrong about whether something is actually a problem *in this codebase*. Every finding is checked against the code before anything is edited. ## Arguments - `<pr-url>` — a full URL such as `https://github.com/owner/repo/pull/42`. **This form works from anywhere** — any directory, inside a different project, or outside a repository entirely. The skill works out which repository it belongs to and gets itself a working copy. - `<pr-number>` — a bare number. Only valid when the current directory is a clone of the repository that owns the pull request, since there is nothing else to resolve it against. - `--repo <owner/name>` — pair with a bare number to target another repository without a URL. - `--in <path>` — where to put a working copy when one has to be created. Defaults per step 4. - `--dry-run` — analyse and report verdicts, change nothing. Good for a first look, and it never needs a working copy at all. Required either way: there is no default target. This skill changes files and pushes. ## Step 1 — Work