Turn a pull request diff into review notes and a risk checklist

Cursor reads a PR diff and drafts review comments plus a short checklist of what could break in production.

Review notes with file references, ordered by risk, and a checklist you can tick before you approve.

1. 1

   Point Cursor at the branch

   Open the PR locally or paste the diff with enough context that file paths resolve.

2. 2

   Post the top risks only

   Leave the highest-severity comments on the review. Move the rest to your own notes if they are nitpicks.

3. 3

   Run the checklist yourself

   Tick every risk item against the running app or tests. A generated checklist is not an approval.

I am reviewing this pull request. Read the diff and the code around the changed lines.

Return two sections:

## Review comments
At most eight comments. Each comment includes:
- File and line or function
- What can go wrong for users or the next maintainer
- The smallest change that would address it

Order comments by severity. Skip formatting, naming taste, and praise. If a change needs a test, say what the test should assert. If the diff is safe, say so and name residual risk.

## Risk checklist
A checklist of 5-8 items I should verify before merge, phrased as yes/no questions I can answer from the diff or a quick manual test. Include auth, data migration, rollback, observability, and config if relevant.

Do not rewrite the pull request. Do not invent tickets, users, or incident history.

Models miss subtle concurrency and permission bugs. Read auth and data paths yourself even when the checklist is green.

Sample case written by Hidden Logic Lab. Not affiliated with Cursor.