pstack for GitHub Copilot

Engineering playbooks, not just code generation

Start with a goal and a way to verify it. The /poteto-mode skill selects a playbook and coordinates the skills and agents needed for the task. Workflows cover investigation, bug fixes, feature development, code review, performance work, and longer autonomous runs.

Choose the models used for delegated work and review panels with /setup-pstack. The port also includes Azure DevOps pull request workflows in place of upstream's Graphite stacking and GitHub review flows.

pstack Copilot is an independent port of pstack for Cursor by poteto. It is MIT-licensed and adapted to Copilot, not a mirror of the Cursor plugin.

Install pstack for GitHub Copilot

You need Git, Node.js, and the GitHub Copilot CLI with access to the models you select. In a POSIX shell, clone the project, register its skills, and copy its agents:

git clone https://github.com/doublexmax/pstack-copilot ~/.copilot/pstack
copilot skill add ~/.copilot/pstack/skills
mkdir -p ~/.copilot/agents
cp ~/.copilot/pstack/agents/*.agent.md ~/.copilot/agents/
copilot skill list

For always-on mode, run the installer. It updates your Copilot instructions, path trust, shell wrapper, and runtime hooks. Preview the changes first if needed:

node ~/.copilot/pstack/scripts/install-always-on.mjs --dry-run
node ~/.copilot/pstack/scripts/install-always-on.mjs

Then start Copilot and run /setup-pstack to choose your models. See the setup guide for Windows, permissions, context policy, and uninstall instructions.

Two tasks to try

Investigate and fix a bug

/poteto-mode the export writes duplicate rows when a retry lands mid-run.
Reproduce it first, fix the root cause, and verify the result.

Review a change before shipping

/poteto-mode review this PR for correctness and regressions.
Explain the evidence for each finding and what still needs verification.

You do not need to name every skill or prescribe the delegation plan. Describe the outcome and what would prove it works.