pstack: make Claude Code prove every bug fix

pstack is a free plugin for Claude Code. It is a port by Michael Denyer of Lauren Tan's pstack, a set of skills built for Cursor, and it also works with Codex, Pi and GitHub Copilot. You tell its main skill, poteto-mode, what you want done, and it picks the right workflow and keeps the work simple and verified.

What pstack-claude does for you: when you ask poteto-mode to fix a bug, it reproduces the failure first. Then it asks how and why the bug happens, hands off the fix, and reruns the exact case that broke. You get the fix plus the failing and passing evidence, so you do not have to take Claude's word for it.

How to install pstack-claude: copy the repo URL below, paste it into Claude Code, and say: install this.

Or install it by hand. Run these two lines in Claude Code (it needs a recent version of Claude Code):

Best practices for pstack-claude:

• Name poteto-mode in your request. The README's own example starts with: Use poteto-mode to fix the search filter resetting when I change pages.
• Describe the bug in plain words, the way you would tell a coworker. Say what you did and what went wrong.
• Ask to see the failing and passing evidence, and read it before you accept the fix.
• Run setup-pstack once to turn automatic routing on or off and to pick models for each job.
• Try /interrogate on a change you are nervous about. It has three different models try to break it.

Prompts to try with pstack-claude:

• Start with poteto-mode on one real bug. It is the main skill and it routes the rest for you.
• Try /arena when you want several attempts at the same task, with the best parts kept.
• Try /bro when Claude's answer is too technical. It restates the last message in plain human language.
• Try /unslop on any writing that sounds like an AI wrote it.