obra/superpowers

systematic-debugging

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

246K installs 281K starsUpdated Sep 1, 2026License: MIT

Install

npx skills add obra/superpowers@systematic-debugging

Runs in your terminal. Adds the skill globally for Claude Code, Cursor, Codex and others; add -g -y to skip prompts.

What it does

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 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 -…

Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.

View source on GitHub

Before you install

Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.

Categories

Related skills

  • brainstorming

    obra/superpowers

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    349K installs 281KDesign & UI
  • writing-plans

    obra/superpowers

    Use when you have a spec or requirements for a multi-step task, before touching code

    238K installs 281KDesign & UITestingDocumentation
  • using-superpowers

    obra/superpowers

    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

    234K installs 281K
  • requesting-code-review

    obra/superpowers

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    218K installs 281KCode reviewGit & GitHub
  • executing-plans

    obra/superpowers

    Use when you have a written implementation plan to execute in a separate session with review checkpoints

    201K installs 281KAI & agentsCode review
  • Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    198K installs 281KTesting

Search skills

/skills/obra/superpowers/systematic-debugging/