systematic-debugging

This skill enforces a disciplined debugging process: establish a tight feedback loop that reproduces the exact symptom, gather evidence across system boundaries, trace data flow to its source, and form testable hypotheses before proposing any fix. By completing each phase sequentially—root cause investigation, pattern analysis, hypothesis testing, and verification—you eliminate guesswork and prevent quick patches from masking deeper issues.

Debugging Protocol teaches a disciplined four-phase investigation process that enforces root cause analysis before any code change. It prevents the common trap of jumping to fixes without understanding why problems exist, using the Iron Law (investigate first) and Three Strikes Rule (escalate after three failed attempts) to guide systematic problem-solving.

Systematic Debugging enforces a disciplined four-phase process: investigate root cause, analyze patterns, form and test hypotheses, then implement fixes. It stops you from guessing at solutions and catching yourself in cycles of failed patches that mask underlying problems.

This skill enforces a disciplined debugging methodology that prioritizes root cause discovery over quick patches. Work through four phases—investigation, pattern analysis, hypothesis testing, and implementation—completing each before advancing. The framework prevents the trap of symptom-fixing by requiring evidence gathering across component boundaries and data flow tracing before any fix attempt.

Systematic Debugging teaches a disciplined four-phase process for tackling any technical issue—from test failures to production bugs. By enforcing root cause investigation before attempting fixes, it eliminates guesswork and the cycle of symptom-patching that creates new problems. The framework emphasizes evidence gathering, pattern analysis, hypothesis testing, and architectural questioning when multiple fixes fail.

Bug Hunt Swarm deploys four read-only sub-agents in parallel to investigate bugs, regressions, and crashes from different angles—reproduction scope, code paths, recent changes, and proof strategies. The main agent then synthesizes findings into ranked hypotheses with supporting evidence and the fastest path to confirm or disprove each theory, all without making code edits.