PR review checklist

---
name: pr-review-checklist
description: "Reviews a pull request or diff for correctness, security, tests and readability, and returns prioritized findings. Use when the user asks to review a PR, a diff, or changes before merging."
---

# PR review checklist

## Workflow

1. Read the PR description and the full diff. Note the intent in one sentence.
2. For each changed file, check the items below. Read the surrounding code when a change depends on it.
3. Report findings ranked by severity: **blocker**, **should fix**, **nit**. Skip categories with no findings.

## Checks

- **Correctness:** off-by-one, null/undefined paths, error handling, race conditions, changed behavior for existing callers.
- **Security:** untrusted input reaching queries, shell, HTML or file paths; secrets in code or logs; missing auth checks.
- **Tests:** new logic has a test; edge cases and failure paths are covered; tests assert behavior, not implementation.
- **Readability:** names say what things are; no dead code; comments explain why, not what.

## Output format

```
### Blockers
- path/to/file.ts:42 — <problem>. <why it matters>. Fix: <suggestion>.
### Should fix
...
### Nits
...
```

End with one line: approve, approve with changes, or request changes.