Leave code review notes on the risky lines

Cursor drafts code review comments for someone else's pull request, limited to behavior, missing tests, and risk.

Comments with a file and a line, ordered so the author knows what to fix before style.

1. 1

   Open the pull request

   Point Cursor at the branch. Comments that do not name a file do not get posted.

2. 2

   Drop the style notes

   Keep comments a maintainer would still want next month. Delete the rest.

3. 3

   Post the top three

   Leave those on the review. Mention the others only if the author asks.

I am reviewing someone else's pull request. Draft comments I can leave for the author. Read the diff and the code around it.

Return at most six comments. Each comment has:
- File and the line or function
- What can go wrong, in plain language
- The smallest change that would answer it

Order them by risk to users or to the next person who edits this. Skip formatting, naming taste, and praise. If a change has no test and needs one, say what the test should assert. If the diff is safe, say so and name the residual risk. Do not rewrite the pull request.

A comment is a question the author can answer. You still approve or request changes yourself.

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