When should I question my software architecture instead of fixing a bug?

According to this skill's protocol, if three or more fix attempts fail, you should stop and discuss whether the underlying architecture or pattern is fundamentally flawed.

What are the four phases of the systematic debugging process?

The process involves Phase 1: Root Cause Investigation, Phase 2: Pattern Analysis, Phase 3: Hypothesis and Testing, and Phase 4: Implementation.

What is the primary benefit of systematic debugging?

It eliminates 'guess-and-check' behavior, ensuring you identify the actual root cause of a bug before writing any code, which prevents regressions and saves time in the long run.

How does this skill handle complex microservices or layered systems?

The skill guides Claude to add diagnostic instrumentation at every component boundary to log input/output and verify state, revealing exactly which layer is failing.

Does this skill help with writing tests?

Yes, it mandates creating a minimal, reproducible failing test case before any fix is implemented to verify the solution and prevent the bug from returning.

Systematic Debugging

Name: Systematic Debugging
Author: tajohnson

bytajohnson

0•

安全与测试

Enforces a rigorous four-phase debugging protocol to identify root causes and eliminate guess-driven fixes in complex software systems.

The Systematic Debugging skill for Claude Code transforms the debugging process from a trial-and-error exercise into a disciplined engineering workflow. By mandating a strict sequence of Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Verified Implementation, it ensures that developers fully understand the 'why' behind an error before changing code. This approach is particularly powerful for resolving intermittent test failures, complex multi-component regressions, and architectural flaws that superficial patches often fail to address.

主要功能

010 GitHub stars

02Multi-component diagnostic instrumentation for tracing data across system boundaries

03Architectural review triggers that activate after three failed fix attempts

04Evidence-based root cause investigation using stack traces and environment logs

05Strict four-phase debugging protocol to prevent superficial 'symptom fixing'

06Test-driven resolution requiring a reproducible failing test case before implementation

使用场景

01Resolving recurring bugs that have resisted previous 'quick fix' attempts

02Troubleshooting intermittent failures in CI/CD pipelines or distributed systems

03Debugging complex data flow issues across multiple service layers or APIs

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tajohnson/superpowers systematic-debugging

For use in Claude.ai and ChatGPT

主要功能

010 GitHub stars

02Multi-component diagnostic instrumentation for tracing data across system boundaries

03Architectural review triggers that activate after three failed fix attempts

04Evidence-based root cause investigation using stack traces and environment logs

05Strict four-phase debugging protocol to prevent superficial 'symptom fixing'

06Test-driven resolution requiring a reproducible failing test case before implementation

使用场景

01Resolving recurring bugs that have resisted previous 'quick fix' attempts

02Troubleshooting intermittent failures in CI/CD pipelines or distributed systems

03Debugging complex data flow issues across multiple service layers or APIs

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tajohnson/superpowers systematic-debugging

For use in Claude.ai and ChatGPT