pr-reviewlisted

# /pr-review — one-shot read-only PR review This is the thin entry point the [`pr-reviewer`](../../../agents/pr-reviewer.md) agent's own documentation already promises (`Trigger with /pr-review <PR-URL|#n>`), and it does exactly one thing: dispatch that agent at a PR and report what came back. It **never applies a finding, never pushes, and never resolves a thread**. That is the whole distinction from its neighbours, and it is the reason to reach for this command rather than one of them: you get a review, and your working tree is exactly where you left it. ## Contents - [Operations](#operations) - [Step 0: Parse the argument](#step-0-parse-the-argument) - [Step 1: Resolve the PR](#step-1-resolve-the-pr) - [Step 2: Dispatch the agent](#step-2-dispatch-the-agent) - [Step 3: Report](#step-3-report) - [`remember` — write a maintainer relevance rule](#remember--write-a-maintainer-relevance-rule) - [Which review command do I want?](#which-review-command-do-i-want) - [Hard rules](#hard-rules) --- ## Operations Parse the **first token** of `$ARGUMENTS`. | First token | Operation | Runs | | --- | --- | --- | | `remember` | [memory write](#remember--write-a-maintainer-relevance-rule) | one `mcp__lorekit__memory_write`, no review | | anything else (or empty) | [review](#step-2-dispatch-the-agent) | one `pr-reviewer` dispatch, read-only | There is no third operation, and no mode flag that turns this command into an apply pass. A request to fix what the review found is [`/review-