What is the 'Iron Law' of this debugging skill?

The Iron Law states: 'No fixes without root cause investigation first.' This prevents 'thrashing' and wasting time on incorrect hypotheses.

When does this skill suggest questioning the software architecture?

If three or more fix attempts fail, the skill identifies a potential architectural problem rather than a simple bug, prompting a deeper discussion about the system design.

Why does this skill prevent me from proposing immediate fixes?

Quick patches often mask symptoms rather than solving the underlying root cause. This skill enforces a 'root cause first' policy to ensure bugs are fixed permanently without creating new issues.

What happens if a bug cannot be consistently reproduced?

The skill directs you to gather more evidence and diagnostic data through instrumentation rather than guessing, ensuring you have a reliable baseline before attempting a fix.

How does this skill handle multi-component systems?

It provides a specific framework for adding diagnostic instrumentation at component boundaries to identify exactly where data flow breaks down between services or layers.

Systematic Debugging

Name: Systematic Debugging
Author: as4584

byas4584

セキュリティとテスト

Enforces a rigorous, evidence-based methodology to identify root causes and implement permanent fixes for technical issues.

概要

The Systematic Debugging skill transforms Claude's problem-solving approach from high-speed guesswork to a structured, scientific methodology. By mandating a strict four-phase process—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation—it ensures that symptoms are never mistaken for causes. This skill is essential for resolving complex bugs in multi-component systems, providing specific frameworks for diagnostic instrumentation, data flow tracing, and architectural questioning when traditional fixes fail to stick.

主な機能

Deep data flow tracing techniques to locate the original source of bad values.
Integration with Test-Driven Development (TDD) to ensure fixes are verified and permanent.
Architectural safety checks that trigger when three or more fix attempts fail.
Multi-component diagnostic instrumentation for tracing errors across system boundaries.
0 GitHub stars
Mandatory four-phase debugging workflow to prevent 'guess-and-check' behavior.

ユースケース

Investigating deep-seated data corruption issues within large call stacks.
Fixing persistent bugs that have resisted multiple previous 'quick fix' attempts.
Resolving intermittent failures in complex CI/CD pipelines or distributed services.

概要

主な機能

Deep data flow tracing techniques to locate the original source of bad values.
Integration with Test-Driven Development (TDD) to ensure fixes are verified and permanent.
Architectural safety checks that trigger when three or more fix attempts fail.
Multi-component diagnostic instrumentation for tracing errors across system boundaries.
0 GitHub stars
Mandatory four-phase debugging workflow to prevent 'guess-and-check' behavior.

ユースケース

Investigating deep-seated data corruption issues within large call stacks.
Fixing persistent bugs that have resisted multiple previous 'quick fix' attempts.
Resolving intermittent failures in complex CI/CD pipelines or distributed services.