PUBLIC · REVIEW & REFINE

Review a change before it ships

Look for meaningful defects, with evidence and a clear fix.

When to use it

Before merging or approving a change you did not write, or one you wrote quickly.

What to expect

Findings ranked by severity, each with its location, the condition that triggers it, the user impact, a minimal correction, and a check that fails before the fix and passes after.

Example

A change to the password-reset flow that touches the email template and the token lifetime.

Add your context

Optional. Leave fields blank to copy a reusable template. What you type stays in this tab.

change or diffsystemrequirementsconstraints

PROMPT TEMPLATE

Review {{CHANGE}} in the context of {{SYSTEM}}.

Expected behavior: {{REQUIREMENTS}}
Relevant constraints: {{CONSTRAINTS}}

Inspect correctness, permissions, data integrity, compatibility, and failure handling. Trace each suspected issue through the relevant caller and downstream behavior. Distinguish confirmed defects from unresolved concerns.

For each finding, report severity, location, triggering conditions, user impact, and a minimal correction. Propose a targeted check that would fail before the fix and pass afterward. Avoid speculative style complaints.

Do not modify files. If no actionable findings exist, say so and list what you could not verify.

4 of 4 context fields remaining.

Free to copy. Use it in the tools you already have.

← Back to the library