review-prlisted

# PR Review Pipeline Orchestrate a full PR review using the `reviewer` MCP server tools. The deterministic tail (policy gate, line grounding, dedup, idempotency, comment cap, publishing) is handled by `publish_review` — your job is analysis quality, not formatting rules. ## Inputs Parse from $ARGUMENTS: target PR as `owner/repo#N`, `owner/repo N`, or a GitHub PR URL. `--dry-run` flag → pass `dry_run=true` to publish_review and show the report instead of posting. **Include resolution (applies to all steps below).** When you read any `references/*-prompt.md` file to dispatch a subagent (steps 3, 4, and 5 — analyze, requirements, risk changes, blast-radius, verify), it may contain `<!-- include: _common/<file>.md -->` markers. Before putting the prompt into the subagent, replace each marker with the verbatim contents of that file (path is relative to `plugin/skills/`). These `_common/*.md` files are the single source of the shared findings-schema / anti-hallucination / tool-usage blocks. ## Pipeline 1. **Prepare.** Call `prepare_review(repo, pr)`. The payload contains: - `pr`: `{number, title, body, base_sha, head_sha, base_ref, draft}` - `policy`: `{severity_threshold, min_confidence, max_comments, categories, ignore, output_language}` - `units`: list of `{path, patch, commentable_right, commentable_left}` - `task_board`: `{type, project, key_pattern, create_target, done_target, options}` or null — non-secret generic board metadata from `.review.yml` -