Can this skill help with complex distributed systems?

Yes, it includes specific protocols for adding diagnostic instrumentation at component boundaries to identify exactly where data or configurations are failing.

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

Absolutely. Phase 4 of the process requires creating a failing test case that reproduces the bug before any fix is implemented to ensure verification.

Why use a systematic process for simple bugs?

Even simple bugs have root causes. Following a systematic process ensures that the fix is correct, documented, and doesn't introduce side effects, often proving faster than manual checking.

How does this skill prevent Claude from making random guesses?

It enforces 'The Iron Law,' which strictly forbids proposing any code changes until the Root Cause Investigation phase is completed and evidence is gathered.

What happens if a bug is too difficult to fix in a few attempts?

If three fix attempts fail, the skill stops the debugging loop and prompts a fundamental architecture review, preventing endless thrashing.

Systematic Debugging

Name: Systematic Debugging
Author: alchimie-di-circe

byalchimie-di-circe

•

安全与测试

Enforces a rigorous, root-cause-first methodology to eliminate guesswork and resolve complex software bugs permanently.

The Systematic Debugging skill provides a disciplined framework for Claude to tackle technical issues, moving away from 'guess-and-check' patches toward evidence-based solutions. By mandating a four-phase process—Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Verified Implementation—it ensures that developers understand exactly why a failure occurs before a single line of code is changed. It is particularly effective for complex, multi-component architectures like Electron apps, offering specialized protocols for diagnostic instrumentation across system boundaries and data flow tracing.

主要功能

01Integrated verification workflow requiring a failing test case before any fix is applied.

02Backward data flow tracing to locate the original source of corrupted state or logic errors.

03Architectural red-flag detection that triggers a design review after three failed fix attempts.

04Multi-component diagnostic instrumentation for tracing errors across CI, build, and API layers.

05Enforces 'The Iron Law': No fixes allowed without documented root cause evidence.

061 GitHub stars

使用场景

01Resolving deep-seated logic errors in complex data pipelines or multi-layer applications.

02Debugging intermittent race conditions or environment-specific failures in production.

03Standardizing troubleshooting steps across a team to prevent 'quick fixes' from creating regressions.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add alchimie-di-circe/extractor-desktop-app systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill