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

The Iron Law states that no fixes can be proposed or implemented until a complete root cause investigation (Phase 1) has been successfully performed.

How does this skill handle complex microservices?

It uses diagnostic instrumentation at every component boundary to log data flow and environment state, revealing exactly which layer is failing.

Is this approach slower than quick patching?

While it requires more initial analysis, it is significantly faster than the 'thrashing' caused by random fixes, resulting in a 95% first-time fix rate.

What happens if a fix doesn't work the first time?

The skill returns to investigation. If three fixes fail, it triggers an architectural review to see if the underlying pattern is fundamentally flawed.

Does it require other skills to function?

It integrates specifically with root-cause-tracing for deep stack analysis and test-driven-development for creating failing test cases.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: franroa

byfranroa

보안 및 테스팅

Implements a rigorous four-phase methodology to identify root causes and ensure reliable software fixes before proposing code changes.

소개

The Systematic Debugging skill transforms how Claude handles technical issues by enforcing a scientific approach to troubleshooting. Instead of applying quick patches that mask underlying problems, this skill follows an 'Iron Law' requiring comprehensive root cause investigation first. It guides the AI through evidence gathering, pattern analysis, and hypothesis testing, ensuring that every fix is backed by data and verified through testing. This approach is particularly effective for complex, multi-component systems and high-pressure environments where 'guess-and-check' methods often lead to regressions.

주요 기능

Multi-layer diagnostic instrumentation for complex system boundaries.
Architectural review trigger after three failed fix attempts to prevent thrashing.
Four-phase framework: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
Mandatory evidence gathering to ensure consistent reproducibility.
0 GitHub stars
Integration with Test-Driven Development (TDD) for verified resolutions.

사용 사례

Resolving complex bugs where previous fix attempts have failed or caused regressions.
Debugging intermittent failures in CI/CD pipelines or multi-service architectures.
Investigating production issues where the root cause is obscured by multiple layers of abstraction.

소개

주요 기능

Multi-layer diagnostic instrumentation for complex system boundaries.
Architectural review trigger after three failed fix attempts to prevent thrashing.
Four-phase framework: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
Mandatory evidence gathering to ensure consistent reproducibility.
0 GitHub stars
Integration with Test-Driven Development (TDD) for verified resolutions.

사용 사례

Resolving complex bugs where previous fix attempts have failed or caused regressions.
Debugging intermittent failures in CI/CD pipelines or multi-service architectures.
Investigating production issues where the root cause is obscured by multiple layers of abstraction.