← ClaudeAtlas

debugginglisted

Systematic debugging methodology — runtime errors, test failures, logic bugs, performance issues, production incidents. Five-step framework, root-cause analysis, browser/Node/Svelte tooling, and common bug patterns.
JasonWarrenUK/goblin-mode · ★ 5 · Code & Development · score 70
Install: claude install-skill JasonWarrenUK/goblin-mode
# Systematic Debugging Methodical approach to identifying and fixing software issues. Emphasises reproducibility, isolation, and verification over trial-and-error debugging. Covers browser DevTools, Node debugging, logging strategies, and Svelte-specific debugging techniques. ## When This Skill Applies Use this skill when: - User reports something "not working" - Investigating errors or unexpected behaviour - Performance issues need diagnosis - Setting up debugging infrastructure - Explaining debugging approaches - Teaching debugging techniques - Questions about DevTools or debugging tools ## The Debugging Methodology **Five-step process**: Reproduce → Isolate → Diagnose → Fix → Verify This applies to every debugging scenario without exception. ### 1. Reproduce **Make the bug happen reliably** Can't fix what you can't reproduce. First priority is finding reliable steps to trigger the issue. **Questions to ask**: - What exact steps produce the error? - Does it happen every time or intermittently? - What's the expected vs actual behaviour? - What's the minimal reproduction case? **Document reproduction steps**: ````markdown ## To Reproduce 1. Navigate to `/dashboard` 2. Click "Load More" button 3. Scroll to bottom of page 4. Click "Load More" again **Expected**: More items load **Actual**: Page freezes, console shows error **Frequency**: Happens every time on 2nd click ```` **If intermittent**: - Look for race conditions - Check network timing issues - Consider