What happens if multiple fix attempts fail?

If three or more fixes fail, the skill triggers an 'Architectural Questioning' phase, prompting a shift from fixing symptoms to evaluating whether the underlying system design is fundamentally sound.

Does this skill require automated testing?

Yes, Phase 4 of the process requires the creation of a failing test case that reproduces the bug before any fix is implemented, ensuring the resolution is verifiable and permanent.

How does it handle bugs in distributed systems?

The skill includes specific steps for multi-component systems, requiring diagnostic instrumentation at every boundary to log data entry, exit, and environment state to pinpoint exactly where the failure occurs.

Why does this skill prohibit immediate fixes?

Proposing fixes without a confirmed root cause leads to 'symptom masking,' where the original bug remains and often resurfaces as a more complex issue or a regression later.

Systematic Debugging

Name: Systematic Debugging
Author: maskelog

bymaskelog

•

Security & Testing

Enforces a rigorous, root-cause-first debugging methodology to eliminate guesswork and prevent regressions during the troubleshooting process.

The Systematic Debugging skill provides a structured framework for diagnosing and resolving complex technical issues by mandating a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. By prohibiting 'guess-and-check' fixes, it guides Claude to gather diagnostic evidence, trace data flows across component boundaries, and verify theories with minimal changes before proposing a final solution. This approach is essential for high-pressure environments, distributed systems, and legacy codebases where surface-level symptoms often mask deeper architectural failures.

Key Features

01Mandatory root cause investigation protocols before any code modifications

021 GitHub stars

03Automated failing test case requirement to ensure long-term resolution

04Multi-component diagnostic instrumentation for tracing data across system boundaries

05Pattern-based analysis to compare failing code against known working references

06Scientific hypothesis testing to isolate variables and verify fixes minimally

Use Cases

01Investigating deep-seated logic errors that persist across multiple failed fix attempts

02Resolving intermittent production bugs in complex, multi-layered architectures

03Troubleshooting failing CI/CD pipelines where environmental variables are inconsistent

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add maskelog/daegu_bus_flutter_app systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill