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

The Iron Law dictates that no fix should be proposed or implemented until a thorough Phase 1 Root Cause Investigation is completed and documented.

Does this skill require writing tests?

Yes, Phase 4 of the process requires creating a minimal failing test case before implementing the fix to ensure the solution is verified and permanent.

What happens if three fix attempts fail?

The skill mandates that you stop and question the underlying architecture. If three fixes fail, it's a signal of a fundamental pattern error rather than a simple bug.

When should I use the Systematic Debugging skill?

Use it for any technical issue, including test failures, production bugs, or performance problems, especially when under time pressure or when previous fixes have failed.

How does this skill handle bugs in multi-layer systems?

It implements diagnostic instrumentation at component boundaries to log data entry and exit, allowing you to pinpoint exactly which layer the data becomes corrupted.

Systematic Debugging

Name: Systematic Debugging
Author: cloudfieldcz

bycloudfieldcz

•

Security & Testing

Enforces a rigorous, four-phase debugging methodology to identify root causes and implement stable fixes without guesswork.

The Systematic Debugging skill transforms how Claude approaches technical issues by mandating a structured root-cause-first workflow. It prevents 'guess-and-check' programming by guiding the AI through evidence gathering, diagnostic instrumentation, and hypothesis testing before any code changes are proposed. Whether dealing with elusive race conditions in CI/CD pipelines or deep data flow errors in multi-layered architectures, this skill ensures that every fix addresses the underlying failure rather than just masking symptoms. It includes a critical 'three-strikes' rule that prompts architectural reviews if multiple fix attempts fail, ensuring long-term code health and developer productivity.

Key Features

01Mandatory architectural evaluation after three failed fix attempts to prevent thrashing.

02Integration with Test-Driven Development (TDD) for verified, regression-proof fixes.

03Backward data flow tracing to locate the original source of corrupted state.

04Strict four-phase debugging framework: Root Cause, Pattern Analysis, Hypothesis, and Implementation.

05Diagnostic instrumentation patterns for complex, multi-component system boundaries.

062 GitHub stars

Use Cases

01Investigating intermittent test failures or production bugs in complex microservices.

02Standardizing debugging procedures across a team to ensure evidence-based troubleshooting.

03Resolving 'quick fix' cycles where one patch inadvertently creates new regressions.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add cloudfieldcz/cf-powers systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill