What problem does it solve?
Random, unplanned bug fixes waste hours of engineering time, introduce new issues, and never address the actual underlying root cause of problems, leading to recurring failures and ongoing technical debt.
Core Features & Use Cases
- 4-Phase Structured Workflow: Mandatory step-by-step process from root cause investigation through implementation, ensuring no fixes are attempted before the underlying issue is fully understood.
- Pressure-Resistant Guardrails: Built-in strict rules and explicit language designed to prevent rationalizing shortcuts during emergencies, time crunches, or when quick symptom fixes seem obviously easier.
- Anti-Pattern Guidance: Clear list of common debugging mistakes (such as fixing symptoms, making multiple changes at once, or skipping investigation for "simple" bugs) with explicit redirection back to the correct process.
- Supporting Techniques: Includes ready-to-use reference methods like root cause tracing, defense-in-depth validation, and condition-based waiting for common debugging scenarios like flaky tests or deep call stack errors.
Use this skill for any test failure, production bug, unexpected behavior, or performance issue, especially when time pressure, prior failed fix attempts, or unclear root causes make random fixes tempting.
Quick Start
Use the systematic-debugging skill to investigate the root cause of the failing payment processing test before proposing any fixes.
