What problem does it solve? Debugging under pressure often leads to guess-and-check fixes that mask symptoms instead of resolving the underlying defect. This Skill enforces a disciplined four-phase workflow (investigate, analyze, hypothesize, implement) with an iron law: no fixes without an identified root cause. ## Core Features & Use Cases - Structured Root Cause Analysis: Walks through investigation, analysis, hypothesis formation, and implementation phases so fixes target the actual defect. - Proactive Error Handling: Activates when users report 500 errors, stack traces, unexpected behavior, or regressions like "it was working yesterday". - Scope Guardrails: PreToolUse hooks check a debug scope boundary before edits or writes, keeping investigation changes contained. - Context Recall: Pulls prior investigations, project learnings, and past eureka moments from local gstack artifacts to avoid re-solving known problems. - Use Case: A user reports a production 500 error after a deploy. The Skill gathers evidence, forms and tests hypotheses against logs and code, identifies the root cause, and only then implements a verified fix. ## Quick Start Ask the assistant to investigate why the login endpoint returns a 500 error and find the root cause before fixing it.
