Skip to content
Skill

systematic-debugging

by obra

AI Summary

A debugging methodology booster that enforces root-cause analysis before proposing fixes, helping developers avoid quick patches that mask underlying issues. Useful for anyone working with code in Claude who needs structured debugging processes.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "systematic-debugging" skill in my project.

Please run this command in my terminal:
# Install skill into your project (11 files)
mkdir -p .claude/skills/systematic-debugging && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/SKILL.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/SKILL.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/CREATION-LOG.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/CREATION-LOG.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/condition-based-waiting-example.ts "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/condition-based-waiting-example.ts" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/condition-based-waiting.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/condition-based-waiting.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/defense-in-depth.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/defense-in-depth.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/find-polluter.sh "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/find-polluter.sh" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/root-cause-tracing.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/root-cause-tracing.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/test-academic.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/test-academic.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/test-pressure-1.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/test-pressure-1.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/test-pressure-2.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/test-pressure-2.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/systematic-debugging/test-pressure-3.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/test-pressure-3.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

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

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

` 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 Phases

You MUST complete each phase before proceeding to the next.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 13d ago
Active
Adoption1K+ stars on GitHub
162.8k ★ · Popular
DocsREADME + description
Well-documented

GitHub Signals

Stars162.8k
Forks14.2k
Issues306
Updated13d ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code