Review and verify a fix in Cursor

Use the diff, review tools, and a failing case to decide whether a fix is ready.

Before you start

• A project with a saved baseline and one reproducible problem.
• The exact steps, expected result, actual result, and relevant existing check commands.

Want to do it yourself?

Difficulty

6 out of 10

Estimated completion time

45–120 minutes

Skills you’ll need: Reproduce a bug, inspect the diff, and verify both the original case and a nearby failure case.

I’ll do it myselfI’d rather get help

How this helps your brand

Judge a proposed bug fix by customer behavior and recorded checks. A focused diff and a repeat of the original failure help you decide whether the change is ready for further review.

1. 1

   Step 1: Reproduce before editing

   Repeat the failure and record the smallest sequence that causes it. Ask Cursor to trace that case through the code before proposing a fix.

   If it cannot reproduce the issue, gather the missing environment or input details. A guessed cause is not enough to judge a fix.

2. 2

   Step 2: Keep the fix focused

   Request the smallest change addressing the cause. Watch the diff as edits happen and stop work if it expands beyond the bug.

   Keep your existing local edits separate. Ask Cursor to identify unrelated changes rather than overwriting them.

   Illustrated exampleFrom request to a checkable result

   1. 01Reproduce the bug
   2. 02Review focused diff
   3. 03Verify behavior

3. 3

   Step 3: Review the proposed changes

   Inspect every changed file and ask for a review of the branch or task diff. After an agent task, Review then Find Issues provides Cursor’s dedicated review.

   Investigate each finding against the actual code. Automated review can miss problems, so compare the change with the original failing behavior yourself.

4. 4

   Step 4: Check success and failure

   Repeat the original case and a nearby failure case, then run the project’s relevant checks. For a form fix, also try an invalid submission.

   If the bug remains, return the exact failing evidence and refine the diagnosis. Save a good version only after the checks pass; publishing is a separate step.

   Illustrated exampleCheck the recovery path

   1. Original case passes
   2. 02Nearby failure handled
   3. 03Record check results

Investigate [bug] in this project. Reproduction: [steps]. Expected: [result]. Actual: [result/error]. Establish the cause before editing. Make the smallest fix, preserve my unrelated local changes, review the full task diff, and run [existing checks]. Verify the original case plus [nearby failure case]. Report results and limitations. Do not commit, push, or deploy.