Copy this first
/pstack:interrogate the whole branch, be picky. Don't change anything yet. Don't report small stuff that isn't a real bug or a behavior regression.- “Don’t change anything yet”: it only reads.
- “Don’t report small stuff”: naming and style comments get filtered out up front.
The AI that wrote the code has a hard time seeing its own mistakes. So other models do the review: they set out to break the change, and a problem only counts if they make it happen. They’re the models you set up in /pstack:setup-pstack.
- Model 1
- Model 2
- Model 3
each tries to break it
Where to look after you send it
It only reports. It doesn’t change your code. The report has three parts:
- Intent: what it thinks the change is for. If that’s wrong, skip the rest.
- Findings: problems that passed a second check. Each has a command and its output, and it reran them.
- Dropped: what it threw out, and why.
Only a few lines changed, but you’re nervous: /pstack:blast-radius
It doesn’t list a pile of “possible risks.” It finds the one fact that makes the change safe, then writes real code to prove it. Anything it can’t prove is marked “unproven.”
Say your Chrome extension moved saved items from chrome.storage.sync to chrome.storage.local. You worry existing users lose them after upgrading:
/pstack:blast-radius This branch moves saved items from chrome.storage.sync to chrome.storage.local.
My biggest worry: after an existing user upgrades, are the items they had in sync still there?
Find the fact this change depends on to be safe, write a script that actually runs to prove it, and paste the output.A good result: the key fact is “on first start after an upgrade, old items move to local.” Then a script: add three fake items, simulate an upgrade, check local has exactly three.
If all you get is “after analysis, this change is safe,” reply: “Prove that fact to the level of something that runs.”
Clean up comments and wording before committing
/pstack:no-comments: deletes extra comments. It keeps license headers, docs on public interfaces, outside links the code can’t express, and workarounds forced by outside dependencies./pstack:unslop: strips the AI tone from PR descriptions and commit messages. You can add rules, like/pstack:unslop the PR description, no em dashes.
Once the PR is open: hand it to Babysit
Once a PR is open, checks fail, people comment, and the main branch moves on. Let it watch all that:
/pstack:poteto-mode babysit this PR, get it green.It handles conflicts first, then comments, then checks. To just see where things stand, ask: “/pstack:poteto-mode look at PR 123. What’s still unresolved?”
Stuck?
/pstack:interrogate said “no verified findings.” Was it lazy?
That’s a normal result. Check Dropped. If you have a specific worry, say it, and have it test that one thing.
I think one of the dropped items is real.
Reply: “Write me a repro for the item the second adversary raised in Dropped.” If it reproduces, it’s real.
Babysit got everything green. Why won't it merge?
That’s on purpose. Say “land the stack” or “go ahead and merge.” It first has helpers that didn’t write the code check each PR, then merges from the bottom up.
/pstack:no-comments deleted a comment I wanted.
It only keeps comments about “things we can’t change.” If you disagree, tell it which outside limit the comment is about, and have it decide again.