Does this skill require other plugins or tools?

Yes, it is designed to integrate with root-cause-tracing for deep stack analysis and test-driven-development for creating mandatory failing test cases.

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

The Iron Law dictates that no fix can be proposed until Phase 1 (Root Cause Investigation) is fully completed, preventing premature patches that mask underlying issues.

What happens if multiple fix attempts fail?

If three or more fixes fail, the skill stops the debugging cycle to question the underlying architecture, preventing further thrashing and encouraging a structural refactor.

How does this skill handle complex, multi-layered systems?

It uses specific diagnostic instrumentation at component boundaries—such as logging data entry and exit points across APIs and databases—to pinpoint exactly where a system fails.

Systematic Debugging

Name: Systematic Debugging
Author: nimeshgurung

bynimeshgurung

Seguridad y Pruebas

Enforces a rigorous, four-phase investigation framework to identify root causes and eliminate fragile patches before any code fixes are applied.

Acerca de

The Systematic Debugging skill prevents the cycle of 'random fixes' and technical thrashing by mandating a structured approach to troubleshooting. It guides Claude through a mandatory process: evidence gathering, pattern analysis, scientific hypothesis testing, and test-driven implementation. By following the 'Iron Law' of investigation before action, this skill ensures that solutions address fundamental architectural issues rather than surface-level symptoms, making it essential for resolving complex production bugs, environment-specific failures, and deep-stack data flow problems.

Características Principales

Deep integration with root-cause tracing and test-driven development (TDD) workflows
0 GitHub stars
Architectural safety valve that triggers pattern re-evaluation after three failed fix attempts
Evidence-based verification logic to prevent 'guess-and-check' coding behavior
Diagnostic instrumentation for multi-component systems (CI/CD, API, Database boundaries)
Mandatory four-phase framework: Root Cause, Pattern Analysis, Hypothesis, and Implementation

Casos de Uso

Debugging complex CI/CD pipeline failures and deployment configuration issues
Resolving intermittent race conditions or environment-specific production bugs
Troubleshooting data flow errors that originate deep within a call stack

Acerca de

Características Principales

Deep integration with root-cause tracing and test-driven development (TDD) workflows
0 GitHub stars
Architectural safety valve that triggers pattern re-evaluation after three failed fix attempts
Evidence-based verification logic to prevent 'guess-and-check' coding behavior
Diagnostic instrumentation for multi-component systems (CI/CD, API, Database boundaries)
Mandatory four-phase framework: Root Cause, Pattern Analysis, Hypothesis, and Implementation

Casos de Uso

Debugging complex CI/CD pipeline failures and deployment configuration issues
Resolving intermittent race conditions or environment-specific production bugs
Troubleshooting data flow errors that originate deep within a call stack