Is this skill compatible with Test-Driven Development (TDD)?

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

Why can't I just apply a quick fix with this skill?

Quick fixes often mask symptoms rather than addressing the root cause, leading to recurring bugs and technical debt. This skill ensures stability by mandating investigation first.

How does the '3-fix rule' work?

If three attempts to fix a bug fail, the skill mandates a transition from tactical debugging to architectural questioning to identify fundamental design flaws rather than continuing to patch symptoms.

Can this skill help with multi-service systems?

Yes, it includes specific protocols for adding diagnostic instrumentation across component boundaries (e.g., API to Database) to pinpoint exactly where data flow breaks.

When should I activate the systematic-debugging skill?

Use it for any technical issue, especially under time pressure, when a 'simple' fix has failed, or when you are dealing with unexpected behavior in production.

Systematic Debugging

Name: Systematic Debugging
Author: januarfonti

byjanuarfonti

0•

개발자 도구

Enforces a rigorous, four-phase scientific method to identify root causes and implement permanent fixes for complex technical issues.

The Systematic Debugging skill prevents 'guess-and-check' behavior by mandating a structured investigative process before any code changes are proposed. By guiding Claude through root cause investigation, pattern analysis, hypothesis testing, and verified implementation, it ensures that bugs are solved at their source rather than masked by superficial patches. This skill is particularly valuable during high-pressure emergencies or when dealing with multi-component systems where data flow is obscured across architectural boundaries, helping developers avoid the trap of 'thrashing' through multiple failed fix attempts.

주요 기능

01Mandatory Phase 1 Root Cause Investigation before any fix proposals

02Architectural sanity checks triggered automatically after three failed fix attempts

03Multi-component diagnostic instrumentation for tracing data across boundaries

04Pattern analysis to compare broken code against known working implementations

05Minimalist hypothesis testing to isolate variables and prevent side effects

060 GitHub stars

사용 사례

01Debugging intermittent failures in CI/CD pipelines or multi-service integrations

02Resolving complex regressions where previous quick fixes have failed to stick

03Navigating legacy codebases where data flow and dependencies are not immediately obvious

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add januarfonti/opencode-template-configured systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill