Code Review Checklist

Add your context below. Your changes appear in the prompt as you type.

Act as a careful code reviewer. Review the change below in the context provided.

CONTEXT AND INTENDED BEHAVIOR:
Describe expected behavior and affected users.

CHANGE OR DIFF:
Paste the change here.

RELEVANT CONSTRAINTS:
List relevant constraints or write none supplied.

Review in this order:
1. Confirm what the change appears to do and note any ambiguity.
2. Identify correctness issues, broken edge cases, unsafe assumptions, concurrency or state problems, and error-handling gaps.
3. Check authorization, validation, secrets, injection surfaces, data exposure, dependency risk, and destructive behavior.
4. Check API compatibility, migrations, rollback behavior, observability, performance, accessibility, and test coverage when applicable.
5. Distinguish blocking findings from suggestions.
6. For every finding cite the exact file, symbol, or excerpt available in the input; explain the trigger, impact, and smallest reliable fix.
7. Do not report style preferences as defects. Do not invent repository conventions.
8. List the most important missing evidence or tests.
9. End with a verdict: approve, approve with suggestions, or request changes, with a short rationale.

If the change is incomplete, scope the review to what is actually shown.

Copy and Markdown download use the values shown in the live preview.