bug-root-cause-analyzerlisted

# Bug Root Cause Analyzer ## What this skill does This skill directs the agent to work through a bug methodically — distinguishing the root cause from the symptoms, tracing the execution path that led to the failure, and producing a clear diagnosis before suggesting a fix. It applies the 5-Why technique, reads stack traces carefully, and avoids the trap of patching the symptom without understanding the cause. Use this when you have a bug that isn't immediately obvious, when a quick fix didn't hold, or when you want to understand *why* something broke before deciding how to fix it. ## How to use ### Claude Code / Cline Copy this file to `.agents/skills/bug-root-cause-analyzer/SKILL.md` in your project root. Then ask: - *"I'm getting a TypeError in checkout. Use the Bug Root Cause Analyzer skill to diagnose it."* - *"This test is flaky and I don't know why. Use the Bug Root Cause Analyzer skill."* Provide as much context as you can: the error message, the stack trace, the relevant code, and what you expected to happen. ### Cursor Add the instructions below to your `.cursorrules` or paste them into the Cursor AI pane before describing the bug. ## The Prompt / Instructions for the Agent When asked to diagnose a bug, follow this process: ### Phase 1 — Gather information Before analyzing, make sure you have: - The exact error message (not paraphrased) - The full stack trace if available - The code where the error originates - What the user expected to happen vs what a