Skip to content

foxytanuki/pstack-opencodex / upstream/skills/poteto-mode

Poteto Mode

Verified

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

FileKindSize
SKILL.mdskill md18.8 KB
playbooks/authoring-a-skill.mdmarkdown831 B
playbooks/autonomous-run.mdmarkdown1.8 KB
playbooks/autopilot-full.mdmarkdown8.7 KB
playbooks/autopilot-stack.mdmarkdown5.1 KB
playbooks/babysit.mdmarkdown8.1 KB
playbooks/bug-fix.mdmarkdown2.2 KB
playbooks/eval.mdmarkdown2.5 KB
playbooks/feature.mdmarkdown2.7 KB
playbooks/hillclimb.mdmarkdown4.0 KB
playbooks/investigation.mdmarkdown928 B
playbooks/multi-phase-plan.mdmarkdown12.8 KB
playbooks/opening-a-pr.mdmarkdown5.2 KB
playbooks/orchestrate.mdmarkdown16.4 KB
playbooks/pause-safely.mdmarkdown1.1 KB
playbooks/perf-issue.mdmarkdown3.0 KB
playbooks/prototype.mdmarkdown2.1 KB
playbooks/refactoring.mdmarkdown3.1 KB
playbooks/runtime-forensics.mdmarkdown1.2 KB
playbooks/session-pickup.mdmarkdown1.6 KB
playbooks/shipping.mdmarkdown5.3 KB
playbooks/trace-forensics.mdmarkdown1.8 KB
playbooks/visual-parity.mdmarkdown1.2 KB
playbooks/worktree-cleanup.mdmarkdown2.9 KB
references/bugbot-triage.mdmarkdown9.4 KB
scripts/bootstrap.tsscript1.7 KB
scripts/bun.lockother6.5 KB
scripts/check-plan.mjsexecutablescript7.5 KB
scripts/orch/orch.test.tsscript18.0 KB
scripts/orch/orch.tsexecutablescript15.1 KB
scripts/orch/store.tsscript41.9 KB
scripts/package.jsonmanifest352 B
scripts/watch-pr/cli.test.tsscript6.0 KB
scripts/watch-pr/cli.tsscript6.8 KB
scripts/watch-pr/fakes.test-helper.tsscript2.9 KB
scripts/watch-pr/github.test.tsscript8.8 KB
scripts/watch-pr/github.tsscript23.5 KB
scripts/watch-pr/policy.test.tsscript12.1 KB
scripts/watch-pr/policy.tsscript24.5 KB
scripts/watch-pr/render.tsscript6.9 KB
scripts/watch-pr/tsconfig.jsonconfig270 B
scripts/watch-pr/types.compile.tsscript2.2 KB
scripts/watch-pr/types.tsscript12.1 KB
scripts/watch-pr/watch-prexecutablescript211 B
scripts/worktree-audit.shexecutablescript3.9 KB

playbooks/bug-fix.md

View on GitHub
### Bug fix

**You own this task. Plan, review, verify.** Delegate investigation and the fix to subagents, stay in the lead.

Be scientific. Every shipped line traces to runtime evidence. Belt-and-suspenders that "might help" is a hypothesis, not a fix. It does not ship. When evidence refutes a hypothesis, revert what it motivated. The smallest change the evidence justifies ships, nothing more.

1. Reproduce it yourself on the matching surface via the control skill (Non-negotiables), even when a debug or instrumentation protocol says to ask the user to reproduce. Ask the user only with a stated, specific reason the control surface cannot reach the target, and only after driving it as far as it goes. If it won't reproduce directly, synthesize the trigger, tighten conditions, or instrument until it fires.
2. Binary-search the cause. Form the candidate hypotheses, then rule them out until one survives. Seed them with `how` over the affected subsystem and the **why** skill for regression history. Each pass, take the split that cuts the most remaining problem space, get runtime evidence, eliminate. When program state is unclear, add instrumentation or logging and read it as the code runs. Don't guess. Drive a long or stubborn hunt with Cursor's `/loop` command. Confirm the surviving *mechanism* with runtime evidence before the step-3 architect/interrogate fan-out.
3. Plan the fix. If it crosses a function boundary, `architect` first. Delegate implementation to a subagent using your configured bug-fix model (default `grok-4.7-xhigh-fast`) with a specific scope.
4. Verify on the same surface. The original repro now passes. "Inconclusive" or wrong-surface is not a pass. Flag it. Unit tests show branch behavior, not bug absence.
5. Stage the commits so the failing repro lands before the fix in git history. See the **tdd** skill for the failing-test-first cadence when the bug has a cheap local test path. Skip it when the test would be expensive, integration-heavy, or unclear.
   This is the canonical **sequence-verifiable-units** principle skill, the failing test first and the fix on top.
6. Run **Opening a PR**.

**Reply:** what was broken, root cause, fix, how you verified. Paste failing-then-passing repro output verbatim.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall