systematic-debugging

by obra/superpowers · Coding & Development

Systematically identify and resolve technical issues by investigating root causes before applying fixes.

Lift—not yet benchmarked

Trustsecurity · quality · license · upkeep

Scan Saferisk 0/100

LicenseMITmetadata + link-out

What it does

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

#debugging#problem-solving#testing

Quality judgment

completeness

9.0/10

clarity

8.0/10

trigger quality

8.5/10

examples

6.5/10

structure

8.5/10

overall

8.5/10

A thorough, well-structured debugging process with clear phases, anti-patterns, and escalation logic (3+ failed fixes → question architecture). Trigger conditions are broad and appropriate. Concrete examples are limited to one multi-layer instrumentation snippet; more varied worked examples would strengthen it.

Files (12)

condition-based-waiting-example.ts · 4.9 KBcondition-based-waiting.md · 3.4 KBCREATION-LOG.md · 4.2 KBdefense-in-depth.md · 3.6 KBfind-polluter.sh · 1.9 KBLICENSE · 1.0 KBroot-cause-tracing.md · 5.2 KBSKILL.md · 9.3 KB… 4 more