What problem does it solve? When errors, stack traces, or unexpected behavior appear, developers often jump straight to patching symptoms. This Skill enforces a disciplined four-phase debugging workflow—investigate, analyze, hypothesize, implement—so fixes address the actual root cause instead of masking the problem. ## Core Features & Use Cases - Root Cause First: Follows an iron law of no fixes without an identified root cause, guiding the AI through evidence gathering before any code change. - Proactive Triggering: Automatically activates when users report 500 errors, stack traces, regressions, or phrases like "it was working yesterday". - Session-Aware Workflow: Adapts behavior for interactive, headless, spawned, and Conductor sessions, with structured decision briefs and plan-mode safety gates. - Use Case: A user reports that their app started returning 500 errors after a deploy. The Skill walks through log inspection, hypothesis formation, and verification before any fix is applied. ## Quick Start Ask the assistant to investigate why the application is throwing an error and find the root cause before fixing it.
