What happens if a fix doesn't work after multiple attempts?

The framework instructs you to stop after three failed attempts and question the underlying architecture or assumptions rather than continuing to stack superficial fixes.

What is the 'Iron Law' of this skill?

The Iron Law mandates that no fixes can be proposed or implemented until a thorough root cause investigation is completed and the 'why' behind the bug is fully understood.

When should I use the Systematic Debugging skill?

Use it for any technical issue including test failures, performance bottlenecks, or build errors, especially when under time pressure or when previous quick fixes have failed.

Does this skill help with test-driven development (TDD)?

Yes, Phase 4 of the framework requires creating a failing test case that reproduces the bug before any fix is applied to ensure the solution is verified.

Systematic Debugging

Name: Systematic Debugging
Author: martin-janci

bymartin-janci

•

セキュリティとテスト

Enforces a rigorous four-phase framework to identify root causes and implement test-driven fixes for any software bug.

The Systematic Debugging skill provides a structured methodology for Claude to handle bugs, test failures, and unexpected behaviors by strictly enforcing investigation before implementation. By following the 'Iron Law'—no fixes without root cause investigation—it helps developers avoid superficial symptom fixes and 'guess-and-check' programming. The skill guides the user through root cause investigation, pattern analysis, hypothesis testing, and final implementation with mandatory regression testing, ensuring that every fix is stable, understood, and verified.

主な機能

01Provides a four-phase framework: Root Cause, Pattern Analysis, Hypothesis, and Implementation

021 GitHub stars

03Enforces the 'Iron Law' of mandatory root cause investigation before any code changes

04Guides minimal hypothesis testing to isolate variables during troubleshooting

05Facilitates data flow tracing and multi-component diagnostics

06Mandates the creation of failing test cases to verify fixes and prevent regressions

ユースケース

01Troubleshooting complex race conditions or intermittent test failures in CI/CD pipelines

02Resolving architectural regressions or unexpected behavior after major dependency updates

03Debugging silent data corruption or flow issues across multiple service components

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add martin-janci/claude-marketplace systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill