debug-phase

Systematic debugging involves reproducing the error consistently, isolating its root cause using techniques like binary search or the 5 Whys, implementing a fix that addresses the actual cause rather than symptoms, and adding regression tests to prevent recurrence. This skill guides you through each phase with structured documentation.

Root cause isolation uses techniques like binary search, logging, breakpoints, and the 5 Whys to pinpoint the actual source instead of just symptoms. The skill helps you classify errors by type and severity, then systematically narrow down where the failure originates in your codebase.

Prevention involves documenting the error with a unique ID in error-log.md, adding regression tests to catch the same bug if it reappears, and improving logging or defensive code. This creates a searchable history and ensures the fix is robust enough to stop future occurrences.

Yes. This debugging methodology applies across development, testing, and operations. It works for any reproducible error where you have complete logs and an accessible environment to investigate and validate your fixes.

You need a reproducible error, complete error logs, and an accessible environment where you can test, instrument code, and validate fixes. The skill outputs an updated error-log.md, implemented fixes, new test cases, and workflow state for tracking progress.

The skill standardizes error documentation in error-log.md with unique IDs (ERR-XXXX format), making errors searchable and building a knowledge base. This prevents duplicate debugging work and helps the team recognize and fix similar issues faster.