systematic-debugging

Community

Installation

Terminal

git clone --depth 1 https://github.com/obra/superpowers.git /tmp/systematic-debugging-src
cp -r /tmp/systematic-debugging-src/skills/systematic-debugging ~/.claude/skills/systematic-debugging

Or .claude/skills/systematic-debugging to scope it to one repo.

Summary

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

Systematic Debugging Overview 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 NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST 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…

Questions

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

Claude Code: ~/.claude/skills/systematic-debugging. Codex: ~/.agents/skills/systematic-debugging. Antigravity: ~/.gemini/config/skills/systematic-debugging. Use .claude/skills or .agents/skills inside a repo to scope it to one project.

More from obra/superpowers

Name