skill-debug

It guides engineers through a four-phase debugging process: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. Mandatory quality gates enforce evidence gathering and risk checks to prevent premature fixes and ensure true root causes are addressed.

Begin Phase 1 root cause investigation by listing the error messages and reproducing the bug with a minimal testcase. This initial evidence gathering step is required before advancing to pattern analysis, hypothesis testing, and implementation.

Yes, systematic debugging applies to performance regressions, unexpected behavior, runtime errors, and test failures across codebases, teams, and debugging environments. The four-phase process scales to various software engineering issue types.

Yes, the systematic debugging process supports multi-agent parallel analysis and integrates with existing debugging workflows to coordinate teams. This allows distributed codebase investigation during the pattern analysis and hypothesis testing phases.

Quality gates prevent premature fixes by enforcing phase-by-phase risk checks and evidence verification before advancing. Engineers must complete root cause investigation and hypothesis testing gates before implementation, ensuring fixes address actual root causes rather than symptoms.

The best way to debug across codebases is applying a four-phase systematic process: root cause investigation, pattern analysis, hypothesis testing, and controlled implementation. This disciplined approach reduces time to resolution and avoids ad-hoc patches across teams.