PR Review Slash Command

---
description: Review a pull request and report severity-ranked findings
argument-hint: <pr-number-or-url>
allowed-tools: Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh pr checks:*), Read, Grep, Glob
---

Review pull request $1.

## Gather

1. `gh pr view $1` for the description, and `gh pr diff $1` for the changes.
2. `gh pr checks $1` for CI status. A failing check is a finding; report which one and what it says.
3. Read the project conventions (CLAUDE.md, AGENTS.md, contributing docs) so the review is against this repository's standards, not generic ones.
4. For each changed function, find its callers with Grep. A change that is correct in isolation and breaks an invariant at a call site is the most valuable thing this review can find.

## Review

Check specifically:
- Correctness: unhandled error paths, boundary and off-by-one conditions, null and empty cases, broken invariants at call sites.
- Concurrency: races, missing awaits, shared mutable state, non-atomic read-modify-write.
- Security: injection, missing authorization checks, secrets in code or logs, unsafe deserialization, user input reaching a shell or a query.
- Data: migrations that lose data, backfills without a rollback, changes to a public schema or API contract.
- Tests: does the change have tests that would fail without it. A test that passes against both the old and new code proves nothing.
- Scope: changes unrelated to the stated purpose of the pull request.

## Report

For each finding, in this format, most severe first:

**[blocker|major|minor] Short claim**
- Where: `file:line`
- Failure scenario: the concrete input or state that triggers it, and what goes wrong
- Smallest fix: one sentence

Then a summary line: files reviewed, blockers, majors, minors.

## Rules

- Only report findings you can defend with a failure scenario. Skip style, naming, and anything a linter owns.
- If the change looks correct, say so and list what you verified. An honest empty review is a valid result and a more useful one than invented nitpicks.
- Do not modify any files and do not post anything to GitHub. Print the review here and let me decide what to post.