# Review

Review the current changes for correctness, regressions, maintainability, and potential security issues.

## Instructions

- Inspect the working tree and relevant diff before reviewing.
- Understand surrounding code and existing conventions.
- Look for:
  - correctness problems
  - edge cases
  - regressions
  - error-handling problems
  - security issues
  - API or behavior compatibility problems
  - missing or inadequate tests
  - unnecessary complexity
- Prioritize concrete, actionable findings.
- Do not criticize style unless it materially affects maintainability or project conventions.
- Do not rewrite the code unless explicitly asked.
- Report findings with file and location references when possible.
- If no significant issues are found, say so and mention what was checked.