review-pr

A finding is one claim about the PR: where it applies, what's wrong, and why it matters. A note is a finding the user adds themselves, a file:line and a rough remark; it enters as keep and skips triage. Triage sorts every finding onto a disposition before a word of the review is written. The review lands as a pending review, visible only to the user until they submit it from GitHub.

1. Establish the PR

Take the PR from the invocation; otherwise ask. Read its title, body, base, head SHA, and every existing review thread, from any reviewer. The range every pass reviews runs from the head SHA's merge-base with the base branch to the head SHA.

Done when you hold the head SHA, the range, and the existing threads.

2. Choose the passes

Detect which passes apply:

• /code-review at high effort: always.
• /mattpocock-skills:code-review: always. It finds the spec itself.
• /browser-qa: when the app is browser-driven and the diff touches something a user sees.

Confirm with one multiSelect AskUserQuestion that lists every pass, marking the ones that apply as recommended, each with a one-line reason.

Done when the user has chosen the passes.