2 min lesson
Reject scope creep, then re-prompt tighter
Find the first warning sign. Explain what you would do next.
Check your understanding
Reject scope creep, then re-prompt tighter.
Outcome: One deletion and one addition make the requested change. The tighter prompt limited the patch, and your review confirms it.
Reject scope creep, then re-prompt tighter
Inline edit, recovery loop
5 steps · ~3 min
Read the proposal → Reject → Re-prompt tighter → Read again → Accept
Read this walkthrough as text
Reject scope creep, then re-prompt tighter
Inline edit, recovery loop
SaySame file, but this time the prompt was vague. 'Fix the empty state message.' The proposal has two changes. One is the wording you wanted. The other is a className rename nobody asked for.
SeeThe hunk changes two places. It updates the label string and renames search-empty-title to empty-title.
DoReject it. The file stays unchanged. Accepting scope creep would turn a one-line fix into a refactor another reviewer has to untangle.
Type
Cmd+K, then "Replace 'No results found' with 'No matches yet'"DoRe-prompt with the exact string and the exact replacement, then read the new hunk line by line before touching Accept.
DoAccept the clean hunk.
SeeOne deletion and one addition make the requested change. The tighter prompt limited the patch, and your review confirms it.
Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.