What is the core principle of the Systematic Debugging skill?

The core principle is to always identify the root cause of an issue before attempting any fix. Symptom-level patches are discouraged to prevent regressions and technical debt.

How does this improve developer productivity?

By following a systematic approach, developers avoid the 'thrashing' cycle of trial-and-error, leading to a 95% first-time fix rate and significantly reduced debugging time.

When should I use this skill instead of a quick fix?

This skill should be used for any technical issue, especially when under time pressure, when a 'simple' fix has already failed, or when dealing with complex multi-component systems.

Does this skill help with reproduction of bugs?

Yes, Phase 1 specifically focuses on consistent reproduction and evidence gathering, ensuring you have a reliable way to trigger the bug before proceeding.

What happens if a fix doesn't work after three attempts?

If three or more fix attempts fail, the process requires you to stop and question the underlying architecture rather than continuing to patch symptoms.

Systematic Debugging

Name: Systematic Debugging
Author: lastdays03

bylastdays03

0•

セキュリティとテスト

Enforces a rigorous, root-cause-first framework for resolving bugs by eliminating guesswork and prioritizing evidence-based investigation.

The Systematic Debugging skill transforms Claude into a disciplined troubleshooter by mandating a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. It prevents the common pitfall of 'guess-and-check' coding by requiring developers and the AI to identify exactly why an error occurs before any code is modified. By integrating diagnostic instrumentation, data flow tracing, and mandatory failing tests, this skill ensures that fixes are permanent, reliable, and do not introduce regressions into complex software systems.

主な機能

01Architectural review triggers to detect fundamental design flaws

02Evidence-gathering instrumentation for multi-component systems

03Mandatory test-driven verification for every proposed fix

04Backward data flow tracing to identify original error triggers

050 GitHub stars

06Strict four-phase debugging protocol for disciplined troubleshooting

ユースケース

01Troubleshooting production bugs where previous quick-fix attempts have failed

02Isolating data flow issues across microservices or multi-layer architectures

03Resolving intermittent test failures in complex CI/CD pipelines

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lastdays03/flask_template systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill