fetch-pr-review

# PR review fetcher **Fetch only** — capture the review feedback left on a pull request; never fix code, reply, or judge the comments. Output is a self-contained `.PR-REVIEW.md` a fresh session can pick up and act on (e.g. via `/refine-pr-review`). ## Source & access Identify the platform from the PR URL (host shape) and fetch through the matching MCP server or CLI — e.g. **GitHub MCP / `gh`** for GitHub PRs, **Azure DevOps MCP** for ADO pull requests. Use whichever equivalent tools are connected; tool name prefixes vary by config. If the input is ambiguous, or no matching MCP/CLI is available, ask the user / stop — don't guess. ## Golden rule: never assume — ask Every uncertainty is confirmed with the user before proceeding: a thread's resolved status, the planning directory, the slug, anything ambiguous in between. A plausible guess is a question, not an answer. ## Your task 1. **Resolve the input.** Accept a full PR URL; extract repo/project and PR id. If unrecognizable, ask. 2. **Fetch the PR metadata** — title, description, source/target branch, state, author, linked ticket/work item — and **all feedback**: - inline review threads (file, line, code context, full reply chain); - top-level review verdicts (approve / request changes / …) with their summary text; - general conversation comments; - bot comments (CI, linters, coverage, …) — captured too, but grouped separately from human feedback. 3. **Determine each thread's status** (see Status ...