debugging-systematicallylisted

# Debugging Systematically This skill provides **debugging methodology** — systematic approaches to finding and fixing bugs. It covers the mental models and techniques for effective troubleshooting. **For specific debugging tools**: See `/debug:*` commands. ## Core Debugging Methodology ### The Scientific Method for Bugs 1. **Observe** — What is actually happening? 2. **Hypothesize** — What could cause this? 3. **Test** — Design an experiment to verify 4. **Analyze** — Did the test confirm or refute? 5. **Iterate** — Refine hypothesis and repeat ### The Golden Rule > **Understand before you fix.** Never make changes to code you don't understand. Reading and comprehending the code often reveals the bug. ## Problem Articulation ### Questions to Answer First | Question | Why It Matters | | ---------------------- | ----------------------------- | | What should happen? | Defines the expected behavior | | What actually happens? | Identifies the discrepancy | | When did it start? | Narrows the scope of changes | | What changed recently? | Identifies potential causes | | Is it reproducible? | Determines debugging approach | ### Rubber Duck Method The act of explaining code line-by-line forces you to: - Think through logic sequentially - Surface implicit assumptions - Notice gaps in understanding - Catch inconsistencies **Often, the solution becomes obvious mid-explanation.** ## Hypothesis Formation ### Common Bug Categorie