Can this skill help with non-reproducible bugs?

Yes, it provides specific strategies for gathering evidence and adding diagnostic instrumentation to capture data from intermittent or environmental issues instead of guessing.

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

The Iron Law dictates that no fix should be proposed or implemented until a thorough root cause investigation (Phase 1) is completed and verified with evidence.

When should I use Systematic Debugging?

Use it for any technical issue, including test failures, production bugs, unexpected behavior, or performance problems, especially when a 'quick fix' isn't immediately obvious.

How does this handle complex bugs?

For complex issues involving multiple components or architectural changes, the skill enters a 'Planning Mode' to outline strategies and get user approval before any code is modified.

What happens if a fix fails multiple times?

If three or more fix attempts fail, the skill triggers an architectural review, suggesting that the problem may lie in the fundamental system design rather than a localized bug.

Systematic Debugging Methodology

Name: Systematic Debugging Methodology
Author: FradSer

byFradSer

•

340

•

安全与测试

Implements a rigorous 4-phase debugging framework to identify root causes and prevent regression bugs.

The Systematic Debugging skill transforms how developers approach technical issues by enforcing a scientific methodology that prioritizes root cause investigation over quick patches. By following a structured process—covering investigation, pattern analysis, hypothesis testing, and final implementation—it ensures that bug fixes are permanent and do not introduce unintended side effects. This skill is particularly valuable for complex, multi-component systems where 'guess-and-check' methods often fail, providing a clear path from error identification to verified resolution through evidence-based reasoning and diagnostic instrumentation.

主要功能

01Strict 'Iron Law' enforcement: no code changes allowed without a proven root cause

02Integrated planning mode for complex architectural issues and high-risk changes

03Multi-component diagnostic instrumentation for tracing errors across system boundaries

04340 GitHub stars

05Four-phase scientific debugging framework (Investigation, Analysis, Hypothesis, Implementation)

06Automated red-flag detection to prevent 'guess-and-check' anti-patterns

使用场景

01Troubleshooting intermittent test failures and production regressions

02Refactoring unstable codebases where previous 'quick fixes' have caused technical debt

03Isolating bugs in complex distributed systems with multiple service layers

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add fradser/dotclaude systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill