What problem does it solve? Bug reports often describe symptoms without revealing causes, leading developers to apply speculative patches, null checks, and symptom-level fixes that mask the real defect. This Skill enforces a disciplined, evidence-first debugging methodology that finds and fixes root causes instead of symptoms. ## Core Features & Use Cases - Structured Debugging Method: A six-step process covering reproduction, full stack-trace reading, diffing against working cases, single-hypothesis testing, minimal root-cause fixes, and a circuit breaker after three failed hypotheses. - Anti-Pattern Detection: Flags common mistakes such as adding null checks without asking why, refactoring while fixing, and trusting fixes that merely hide symptoms. - Repo-Specific Gotchas: Documents Nexi-specific pitfalls, including the correct virtualenv interpreter, the three tool-registry lists (_TOOLS, ALLOWED_INTENTS, TOOL_INTENTS) that cause silent tool failures, and dynamic model selection via the model registry. - Use Case: When a tool in the Nexi assistant silently routes to chat instead of executing, use this Skill to systematically check all three registry lists before concluding the tool is broken. ## Quick Start Ask the assistant to apply the Karpathy debugging method to investigate why a specific bug or failing tool occurs before writing any fix.
