# Code Review Checklist

Review a proposed code change for correctness, security, maintainability, and operational risk.

## Prompt

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

CONTEXT AND INTENDED BEHAVIOR:
{{context}}

CHANGE OR DIFF:
{{change}}

RELEVANT CONSTRAINTS:
{{constraints}}

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.

## How to use

Provide the diff plus expected behavior and relevant system constraints. Validate high-severity findings in the repository or tests before acting.

## Examples

Example input: a pull request adding an account-deletion endpoint and database cleanup job.

Expected output: evidence-linked blocking findings, nonblocking suggestions, missing tests, and an explicit review verdict.

## Variables

- context: What the change should accomplish.
- change: The code, diff, or patch to review.
- constraints: Repository conventions, runtime, compatibility, or security requirements.

Version: 1
Author: JRamos / John Ramos
License: All Rights Reserved

Initial original UMG Prompt Library release.