Make a fixture from a sanitized log
Cursor handles this as a draft: Replace emails with placeholders. Do not use production data.
- Steps
- 4
- Cost
- low
- Time
- Half an hour
Unverified · cursor.com · 16 Oct 2026
Loading the catalog…
Loading the catalog…
Cursor Agent adds a failing test for a known bug, then the fix, and stops if the test never failed.
Include inputs and the wrong output. The agent should not have to rediscover the bug.
The agent overview lists terminal commands among the tools. The failure output is required.
A test that only checks 'does not throw' is not a regression test for a logic bug.
The history should show the test was meaningful. You still review the production change.
These are editorial labels so you can compare playbooks. They are not measurements.
No. Status is unverified. Paste the prompt, keep the version that worked, and do not treat the time or cost lines as measurements.
The prompt says to stop when a failing test cannot be made. A flake needs a tighter repro, not a guessed fix.
Official documentation URL, checked when this seed was written. The prompt and steps are an original AI Playbook Gems playbook, not a quotation of a customer story, and have not been re-run.
Machine-readable copy: JSON
Cursor handles this as a draft: Replace emails with placeholders. Do not use production data.
Unverified · cursor.com · 16 Oct 2026
Cursor handles this as a draft: The smallest change that could explain the failure I paste. Do not commit.
Unverified · cursor.com · 15 Oct 2026
Cursor's agent searches the repo, edits the files for one ticket, and runs the checks you name. The ticket's out-of-scope list is part of the prompt.
Unverified · cursor.com · 15 Oct 2026