What problem does it solve? Debugging often devolves into guess-and-check patching that masks symptoms instead of fixing the underlying defect. This Skill enforces a disciplined four-phase workflow—investigate, analyze, hypothesize, implement—with an iron law that no fix ships without an identified root cause. ## Core Features & Use Cases - Structured Root Cause Analysis: Walks through investigation, analysis, hypothesis formation, and implementation phases so fixes address the actual defect. - Proactive Error Triage: Triggers on reports of 500 errors, stack traces, regressions, and "it was working yesterday" scenarios. - Context-Aware Sessions: Loads prior investigations, project learnings, and past eureka moments from the gstack knowledge store to avoid re-solving known problems. - Use Case: A user reports a production 500 error after a deploy. The Skill gathers evidence, forms hypotheses, confirms the root cause, and only then guides the fix. ## Quick Start Ask the agent to investigate why the login endpoint started returning 500 errors after the last deploy.
