Copy this first
/pstack:poteto-mode After a retry, users get two notifications. Reproduce it first, then fix it, then verify.“Reproduce” means making the problem happen again. It does that first. If it can’t, it won’t change the code.
The order is fixed: reproduce, find the real cause, fix it, then verify with the same steps.
- 1Reproduce itMake the problem happen again
- 2Find the real causeThe first place it goes wrong
- 3Fix it thereNot a check added downstream
- 4Rerun the same stepsThe problem is gone
Give it a few more clues
/pstack:poteto-mode Since yesterday's release, CSV export drops the last row. The failing job id is 4812. Reproduce it first, then fix it. It's fixed when the 60,000-row test dataset exports with no rows missing. Show me the row counts before and after the fix.Each part does one job:
- Symptom and when it started: since the release, export drops the last row.
- A clue you have: the job id. It saves a round of searching.
- What counts as fixed: all 60,000 rows export.
- What to show you: row counts before and after.
A Chrome extension example
Users report: saved items in the side panel sometimes show up twice after a refresh.
/pstack:poteto-mode Users report that the saved list in the side panel sometimes shows duplicate items after a refresh.
I tried it myself, and clicking "Save" twice quickly makes it more likely. Reproduce it first. Don't change any code yet.
It's fixed when clicking Save ten times leaves exactly one item in the list, and exactly one in chrome.storage.
Show me what's actually in storage before and after the fix.- “Exactly one in chrome.storage”: the UI might hide duplicates while the data still has two. Check the stored value.
- “Clicking Save ten times”: turns “sometimes” into a check that passes or fails every time.
Where to look after you send it
At the start: its restatement. If it describes a different problem, stop it right away.
In the middle: the todo list. It lists a few possible causes and rules them out, until it finds the first place things go wrong. The fix belongs there, not in a later check.
At the end: before and after. Both use the same repro steps.
Easy to test? Add /pstack:tdd
/pstack:poteto-mode Reproduce the duplicate write first. If there's a cheap test path, use /pstack:tdd: write a failing test, then fix it, then run it again.Keep “if there’s a cheap test path.” A test propped up by piles of fake data proves less than running the real command.
Stuck?
It says it can't reproduce the bug.
That’s good. It isn’t changing things blindly. Be more specific: which page, what data, what you clicked, which version. You can also paste a log or a recording.
It said “fixed” but showed no evidence.
Reply: “apply prove it works. Run the repro steps again and show me the real output.” prove it works means: show real results that it works. It’s the name of a pstack principle. Type it as is, and it knows what you mean.
It added an if check later on and called it fixed.
Reply: “fix root causes. This state should never happen. Find where it first goes wrong.” fix root causes means fix the real cause. It’s also a principle name. A check only counts as a fix if that state is actually valid.