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

# Install skill into your project (11 files)
mkdir -p .cursor/skills/systematic-debugging
&& curl --retry 3 --retry-delay 2 --retry-all-errors -o .cursor/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 .cursor/skills/systematic-debugging/CREATION-LOG.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/systematic-debugging/CREATION-LOG.md"

Run in your IDE terminal (bash). On Windows, use Git Bash, WSL, or your IDE's built-in terminal. If curl fails with an SSL error, your network may block raw.githubusercontent.com — try using a VPN or download the files directly from the source repo.

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.

Quality Score

B

Good

75/100

Standard Compliance45
Documentation Quality72
Usefulness78
Maintenance Signal100
Community Signal100
Scored 4d ago

GitHub Signals

Stars84.2k
Forks6.6k
Issues146
Updated3d ago
View on GitHub

Trust & Transparency

Open Source — MIT

Source code publicly auditable

Verified Open Source

Hosted on GitHub — publicly auditable

Actively Maintained

Last commit 3d ago

84.2k stars — Strong Community

6.6k forks

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code