What problem does it solve? When something breaks and the cause isn't obvious, ad-hoc guessing wastes time. This Skill provides a systematic four-step debugging session that moves from reproduction to root cause to a verified fix. ## Core Features & Use Cases - Structured Four-Step Process: Reproduce the issue, isolate the affected component, diagnose the root cause, and propose a fix with regression tests. - Structured Debug Report: Outputs a consistent report covering expected vs. actual behavior, root cause, fix, and prevention measures. - Connector-Aware Context: When monitoring, source control, or project tracker connectors are available, it pulls logs, recent deploys, and related commits to correlate the issue with recent changes. - Use Case: You paste a production stack trace and mention it started after yesterday's deploy; the Skill narrows the suspect code path, identifies the root cause, and suggests a fix plus a regression test. ## Quick Start Invoke the debug skill with your error message or a description of the problem, such as "/debug this API returns 500 only for large payloads after the latest deploy".
