plugins/pokayokay/skills/systematic-debugging/SKILL.md
Use when diagnosing bugs, failing tests, build failures, unexpected behavior, flaky tests, regressions, or production incidents. Requires reproduction, root cause evidence, one-hypothesis fixes, and regression verification before editing.
npx skillsauth add srstomp/pokayokay systematic-debuggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fix root causes, not symptoms. Do not edit code until you have reproduced the issue or gathered enough evidence to explain why reproduction is impossible.
If the issue cannot be reproduced, gather logs or traces and report the missing data instead of guessing.
Write the hypothesis as: "I think X is the root cause because Y evidence."
verification-before-completion before reporting success.## Debugging Report
### Reproduction
- Command/steps:
- Expected:
- Actual:
### Root Cause
- Hypothesis:
- Evidence:
### Fix
- Files:
- Why this is minimal:
### Verification
- Command:
- Result:
development
Git worktree management for isolated task development
development
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
testing
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
development
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.