pr-reviewlisted

# Pre-landing pull-request review Use before shipping a feature branch: staged or committed changes vs the base branch. Not for post-merge review (that's out of scope; see the managed code-review service). Not for speculative review of in-progress work (too early; most findings will be stale by the time you ship). Activates on: `"review this PR"`, `"code review"`, `"check my diff"`, `"pre-landing review"`, and proactive suggestion when the user describes an imminent merge. ## Before anything else — read REVIEW.md If the repository has a `REVIEW.md` at the root, read it and **honour it as highest priority**. It's how the project scopes reviews to its own concerns. Your findings should respect its severity calibration, nit cap, skip-rules, and always-check list. MARVIN's own `REVIEW.md` lives at the repo root. Any MARVIN session reviewing MARVIN code reads it automatically. ## Scope gate — don't review the wrong thing 1. **Check the base branch.** `git rev-parse --abbrev-ref HEAD` and `git remote show origin | grep 'HEAD branch'`. If the current branch IS the base branch, there's no diff to review — exit politely. 2. **Check for a diff.** `git diff origin/<base>...HEAD --stat`. If zero lines changed, exit — nothing to review. 3. **Scope drift check.** Compare the stated intent (commit messages, PR description if present, TODOs the user mentioned) against the actual diff. Flag scope creep ("branch was supposed to add feature X but also touches Y, Z")