systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/obra/superpowers /tmp/superpowers && ln -s /tmp/superpowers/skills/systematic-debugging ~/.claude/skills/systematic-debuggingFrom README
Systematic Debugging Overview Random fixes waste time and create new bugs. Quick patches mask underlying issues. Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure. Violating the letter of this process is violating the spirit of debugging. The Iron Law If you haven't completed Phase 1, you cannot propose fixes. When to Use Use for ANY technical issue: Test failures Bugs in production Unexpected behavior Performance problems Build failures Integration issues Use this ESPECIALLY when: Under time pressure (emergencies make guessing tempting) "Just one quick fix" seems obvious You've already tried multiple fixes Previous fix didn't work You don't fully understand the issue Don't skip when: Issue seems simple (simple bugs have root causes too) You're in a hurry (rushing guarantees rework) Manager wants it fixed NOW (systematic is faster than thrashing) The Four Phases You MUST complete each phase before proceeding to the next.
More from this repo
requesting-code-review
Used when completing tasks, implementing major features, or before merging to verify work meets requirements
test-driven-development
Used when implementing any feature or bugfix, before writing implementation code
using-superpowers
Used when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY...