pr-resolvelisted

# /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-number-or-url>` — required. There is no default; this skill changes files, so the target must be explicit. - `--repo <owner/name>` — otherwise taken from `origin`. - `--dry-run` — analyse and report verdicts, change nothing. Good for a first look. ## Step 1 — Fetch the pull request ```bash gh pr view <n> --repo <owner/name> --json number,state,headRefName,baseRefName,author,url,headRefOid ``` Refuse if it is not open. Refuse if the author is not you — for someone else's PR, use `/pr-review` and hand them the findings. ## Step 2 — Collect every finding ```bash gh api /repos/<owner>/<repo>/pulls/<n>/comments # inline review comments, with ids gh api /repos/<owner>/<repo>/pulls/<n>/reviews # review bodies, including bot summaries gh api /repos/<owner>/<repo>/issues/<n>/comments # general discussion ``` Sort each into a bucket: - **actionable** — name