What problem does it solve? Debugging often leads to hasty patches that mask symptoms instead of fixing the underlying issue. This Skill enforces a disciplined four-phase workflow—investigate, analyze, hypothesize, implement—with an iron law of no fixes without an identified root cause. ## Core Features & Use Cases - Structured Debugging Phases: Guides the AI through investigation, analysis, hypothesis formation, and implementation in a strict sequence. - Proactive Error Response: Automatically activates when users report errors, stack traces, 500 errors, or unexpected behavior like "it was working yesterday." - Context-Aware Sessions: Loads prior investigations, project learnings, and past eureka moments from the gstack knowledge store to avoid repeating past mistakes. - Use Case: A user reports "the login endpoint returns 500 after the last deploy." The Skill investigates logs and code, forms a hypothesis about the root cause, confirms it, and only then implements a fix. ## Quick Start Ask the AI to investigate why the application is throwing an error and find the root cause before fixing it.
