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

The Iron Law mandates that no code fixes can be proposed or implemented until a thorough root cause investigation (Phase 1) is completed and evidence is gathered.

How does this skill handle complex multi-component systems?

It uses diagnostic instrumentation to log data at every component boundary, identifying exactly where a failure occurs before investigating specific internal logic.

What happens if a bug isn't fixed after three attempts?

The skill triggers an architectural review phase, prompting the user to question the fundamental design patterns rather than continuing to apply symptomatic patches.

Does this skill require Test-Driven Development (TDD)?

Yes, Phase 4 requires the creation of a failing test case before implementing a fix to ensure the solution is verified and prevents future regressions.

Is this framework suitable for production emergencies?

Yes. While it seems more involved, the systematic approach is significantly faster than 'guess-and-check' thrashing during high-pressure incidents.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: yusoofsh

byyusoofsh

安全与测试

Enforces a rigorous four-phase debugging methodology to identify root causes and ensure stable, verified code fixes.

关于

The Systematic Debugging skill provides a disciplined framework for Claude to tackle complex technical issues, preventing the common 'guess-and-check' cycle that leads to technical debt. By mandating a strict progression through root cause investigation, pattern analysis, hypothesis testing, and implementation, it ensures every fix addresses the underlying problem rather than just masking symptoms. This skill is essential for debugging multi-component systems, tracing deep data flow issues, and identifying when a problem is architectural rather than logic-based.

主要功能

Automated architectural health checks triggered after three failed fix attempts
Four-phase structured debugging framework: Investigation, Pattern Analysis, Hypothesis, and Implementation
Integration with Test-Driven Development (TDD) for verified regressions
0 GitHub stars
Mandatory root cause verification before any code changes are proposed
Diagnostic instrumentation for tracing data flow across multi-layered systems

使用场景

Tracing data corruption issues through multiple service boundaries or API layers
Resolving intermittent test failures in complex CI/CD or build pipelines
Handling high-pressure production bugs where random patches could cause further damage

关于

主要功能

Automated architectural health checks triggered after three failed fix attempts
Four-phase structured debugging framework: Investigation, Pattern Analysis, Hypothesis, and Implementation
Integration with Test-Driven Development (TDD) for verified regressions
0 GitHub stars
Mandatory root cause verification before any code changes are proposed
Diagnostic instrumentation for tracing data flow across multi-layered systems

使用场景

Tracing data corruption issues through multiple service boundaries or API layers
Resolving intermittent test failures in complex CI/CD or build pipelines
Handling high-pressure production bugs where random patches could cause further damage