Systematic Debugging sets one law: no fixes without root cause investigation first. The agent works through four phases: read the errors and reproduce the bug, find working examples and compare, form one hypothesis and test it with the smallest change, then write a failing test and fix the cause. Supporting guides cover backward tracing, defense in depth and condition-based waiting.
What You Get
- A four-phase process: root cause, pattern analysis, hypothesis, implementation
- Techniques for tracing bad values back to their source
- A defense-in-depth guide for validating at several layers
- Condition-based waiting guidance with a TypeScript example for replacing arbitrary timeouts
- A shell script that bisects test files to find the one that pollutes state
Common Use Cases
- Investigating a failing test
- Diagnosing a bug that spans several components
- Tracking down a flaky test caused by timing
- Finding the test that leaves stray files behind
What Makes It Unique
It forbids fixes until Phase 1 is complete and names the situations where agents are most tempted to skip it, such as time pressure and repeated failed fixes. A failed hypothesis leads to a new hypothesis, and fixes are never stacked on top of each other.
Under The Hood
Instructions plus four reference files and a bash script, find-polluter.sh, that loops over test files matched by a pattern and checks whether a given file or directory appears. The agent runs your build, test and diagnostic commands and reads git history and logs. The skill ships a TypeScript example for waiting on conditions.