---
name: focused-change-review
description: Review a proposed repository change against a supplied requirement and report actionable findings. Use when the user asks for a review of a specific diff or patch.
---

# Focused change review

## Inputs
- The requested behavior and the diff to review.
- Relevant repository instructions and validation commands.

## Procedure
1. Read the requirement and establish the intended behavior.
2. Inspect each changed file and any callers needed to understand it.
3. Check likely failure paths and distinguish evidence from assumptions.
4. Report findings with a file location, concrete trigger, and consequence.
5. State which checks ran, which could not run, and what remains uncertain.

## Output
A short review, highest-impact findings first. If there are no supported findings,
say so and describe the practical limits of the review. Do not invent problems.

## Boundaries
Do not edit files when the request is only a review.
Do not claim a test passed without observing its result.