01
It starts by itself
test or build fails. Runs in GitHub Actions or Claude Code routine.
- ↻ test or build fails
CI run status == failure
Jesse Vincent · 304K installsPrime Radiant · Keyboardio · Request Tracker, SuperpowersSystematic Debugging skill
Runs by itself, when a test or build fails.
Bugs fixed at the source, not patched over.
Install the Systematic Debugging skill and make it a habit: follow https://gethabit.dev/skills/obra/systematic-debugging.md
- 1Copy
- 2Paste into Claude Code, Codex or Cursor
- 3It runs by itself
304K installs303K starsMIT licenceSource on GitHub ↗
Systematic Debugging
by Jesse Vincent · 304K installs
The skill
Makes your agent find why a bug happens before it fixes it.
Only when you ask.
Fewer bugs
Bugs fixed at the source, not patched over. Fewer bugs come back.
↻ Runs by itselfwhen a test or build fails
How the habit works.
You don't have to.
When does it start? How does it check its work? What does it remember?
One run, step by step.
Then it stops.
Stops after one bug per run, or after three failed fix attempts.
- 01
Investigate root cause
Read the full error and stack trace, reproduce the failure, and check recent changes with git diff.
- 02
Gather evidence
In systems with many parts, log what enters and leaves each part to find where it breaks.
- 03
Compare patterns
Find similar code that works and list every difference from the broken code.
- 04
Test one hypothesis
Write down one cause, then make the smallest change that tests it.
- 05
Write failing test
Use the superpowers:test-driven-development skill to pin the bug in a test that fails.
- 06
Fix and verify
Make one fix at the source, then use superpowers:verification-before-completion before you call it done.
- 07
Escalate after three
If three fixes failed, stop and discuss the architecture with your human partner.
What it may do.
Nothing more.
It writes only in its own folder and asks you before anything goes out.
- Writes only insrc/**, tests/**, loops/systematic-debugging-loop/**
- Talks tono outside service
- Sendsnothing
- Your OKIt asks you before anything goes out.
Is it for you?
Use it when it fits.
Read both lists. If the left one sounds like you, the Systematic Debugging skill helps.
Use it when
- ✓ a test or build fails
- ✓ a bug shows up in production
- ✓ a quick fix already failed
Skip it when
- – you only want a new feature
- – there is no error to investigate
Systematic Debugging skill, answered.
Why not just try a quick fix?
The skill forbids fixes before the root cause is found. Guessing tends to create new bugs and rework.
What happens after three failed fixes?
The loop stops and asks you to question the design with it. A fourth fix needs that talk first.
What if there is no root cause?
If the cause is truly in the environment or timing, the loop records what it checked and adds handling and logging.
How do I install the Systematic Debugging skill?
Copy the prompt at the top into your agent. It installs the skill from obra/superpowers and sets up the habit. Or run npx skills add obra/superpowers --skill systematic-debugging.
Is the Systematic Debugging skill free?
Yes. It is published under MIT. Habit is free too.
Systematic Debugging. Now as a habit.
Install the Systematic Debugging skill and make it a habit: follow https://gethabit.dev/skills/obra/systematic-debugging.md
All Jesse Vincent skills →More code skills →
Works in
- Claude Code
- Codex
- Cursor
- ChatGPT
- Claude app
Made by Jesse Vincent, published under MIT. Habit links to the original and never changes it. Is this your skill?