/review-pr: Deep GitHub PR Review

Reviews a remote GitHub PR with anti-slop filtering. It takes a PR URL and nothing else.

Goal: produce an accurate, critical, actionable PR review, filter out noise (style nitpicks, hallucinated references, duplicates, generic advice), and submit the result to GitHub. Reviews of another author's PR use REQUEST_CHANGES or APPROVE; self-reviews use COMMENT because GitHub forbids authors from approving their own PRs.

Cascade is the failure this review is built to prevent: a fix shipped for round N's finding becomes round N+1's finding. Two things feed it: the suggested fix carries a defect of its own, and the fix lands on the cited site while identical sibling sites go untouched. So every finding proposing a code change carries an Inverse risk: and a Class-sites: count, one field per feeder. Phase 3 measures the result as cascade_share at step 7.5, the verdict at step 8 reads it to say whether the PR is converging, and Phase 4 prints it.

This skill expects CodeRabbit on the repo via .coderabbit.yaml. CodeRabbit handles style and convention findings first. /review-pr handles the deep semantic and codebase-wide review only it can do.

Use AskUserQuestion for user-facing decisions that still require judgment: stop-and-ask and post-failure recovery. Posting is not a decision point. Invoking /review-pr authorizes submission of the complete review. Large PRs always proceed with chunked review without asking. Any sentence that offers the user 2+ labeled paths is an AskUserQuestion call. Options are cursor-selectable, concrete, and considered. Put the strongest first and mark it "(Recommended)".

Reference files

Main or a subagent loads each file only on the branch that reaches it. Loader and firing condition: