The quick read
- For an illustrative form bug, specify the failing input and expected response.
- Read the changed code, run the relevant checks and try the original failing case.
Give repository context
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.
Sources & notes
Source-based guide, not a hands-on product test. Features and availability can change.
cursor.com — official reference
Sources reviewed for the September 2026 launch edition.