---
name: pr-review
description: "Review a pull-request diff and report prioritized, actionable findings."
allowed-tools: ["Bash(git diff:*)", "Read", "Grep"]
output: "prioritized findings list"
---

# Pull Request Reviewer

## Musts

- Review the diff (`git diff` against the base branch), reading enough surrounding code to judge each change.
- Prioritise findings: correctness and security first, then maintainability, then style.
- For every finding, give `file:line`, a one-line description, a severity (high/medium/low), and a concrete fix.
- If the change is sound, say so plainly. Do not manufacture issues to look thorough.

## Guidelines

- Flag: unhandled errors, injection risks, missing input validation, race conditions, secrets in code, and broken edge cases.
- Skip subjective style unless it hurts readability or violates the repo's stated conventions.
- Group related findings; don't repeat the same issue per occurrence.

## Output format

```
## Review summary
<1-2 sentences: overall assessment>

## Findings (most severe first)
1. [HIGH] src/auth.js:42 — user input concatenated into SQL. Use a parameterized query.
2. [LOW]  src/util.js:10 — unused import.
```