← ClaudeAtlas

debuglisted

This skill should be used when the user asks to "debug this", "find the bug", "fix this error", "why isn't this working", "troubleshoot", or when code changes need verification through browser testing.
diegosouzapw/awesome-omni-skill · ★ 42 · Code & Development · score 66
Install: claude install-skill diegosouzapw/awesome-omni-skill
# Debug Workflow Skill This skill implements a systematic debug loop with **runtime logs access**, modeled after Cursor's Debug Mode. ## Core Principle: Evidence-Based Debugging **DO NOT immediately write a fix.** Like Cursor, this workflow requires: 1. Generate hypotheses first 2. Instrument code to collect runtime data 3. Fix based on actual evidence 4. Verify the fix works 5. Clean up all instrumentation ## Task Classification Before starting any work, classify the request: ### Level 1: Minor Tweak (No debug loop, no commit) **Examples:** Font size change, color adjustment, padding/margin tweak, text update **Criteria:** - Single property change in CSS or config - No logic changes - Purely visual/cosmetic - User says "just", "quick", "small", "tweak" **Action:** Make the change, brief confirmation, done. No debug loop, no commit. ``` --- **Minor Tweak** Changed [what] from [old] to [new] in [file] --- ``` ### Level 2: Small Change (Quick verify, no commit unless requested) **Examples:** Add a CSS class, rename a variable, adjust a threshold, fix a typo in logic **Criteria:** - Few lines of code - Low risk of breaking anything - Related to current work (part of previous task) **Action:** Make change, quick browser check for errors, report. No full debug loop. ``` --- **Small Change** Updated [what] in [file] Verified: No console errors --- ``` ### Level 3: Task (Full debug loop if issues, commit when done) **Examples:** New feature, bug fix, refactor, behavior cha