---
name: pr-overview
description: Use when the user explicitly wants a pull request summarized from the actual diff, blockers, and highest-value test guidance.
---

# PR Overview

Review a PR using the actual diff, status checks, and review comments. Do not rely on the PR description as the source of truth.

## Return

1. `What changed`: brief grouped summary based on the diff
2. `Blockers`: only real production blockers; say `None` if there are none
3. `What to test`: specific flows and edge cases driven by the code changes
4. `Comments`: short numbered list of the important review comments only

## Rules

- Keep it short and dense.
- Prioritize correctness, security, and data-loss risk over style.
- Ignore nitpicks.
- Reference files and lines when calling out comments or blockers.