THE DIRECT ANSWER

Describe the bug or feature, the affected behaviour and the constraints of the existing project. Ask the assistant to inspect relevant files before proposing an edit. Include the command or steps that reproduce the problem when available.

Keep the change bounded

For an illustrative form bug, specify the failing input and expected response. Request a focused patch and an explanation of the cause. Avoid mixing a small fix with unrelated refactoring, dependency updates and visual changes unless those are genuinely required.

Review the diff and behaviour

Read the changed code, run the relevant checks and try the original failing case. Test one neighbouring case that could be affected. A successful command is evidence only for what that command actually covers. Check current product settings for model access and repository handling. The useful measure is whether a developer can understand, validate and maintain the resulting change. Code volume and confident explanations are weaker signals than a clear patch that solves the stated problem.

Review a complete repository change

Give Cursor a small bug with a reproducible input and expected output. Ask it to identify the relevant code before editing. After the change, inspect the full diff, run the applicable tests and check that unrelated files were not modified unnecessarily. Repeat with a failure case absent from the initial example. This proposed pilot measures a maintained behaviour change, including review time, rather than counting lines written or judging the explanation accompanying the patch.

COMMON QUESTIONS

Questions readers ask

What should I review after Cursor changes code?

Review the diff, dependencies, tests and edge cases against the task. An agent's explanation is not evidence that the changed application behaves correctly.

SOURCES & NOTES

Follow the evidence.

AI-assisted, source-based workflow guide. The exercise above is a proposed evaluation, not a hands-on test or a scored review. Check current product documentation for features, availability and terms.

  1. cursor.com — official reference

Public sources support the factual background. Analysis and illustrative exercises are identified in the text. How we assess AI · Editorial standards

Spot a factual error or an outdated detail?