What happens if multiple fix attempts fail?

After three failed fix attempts, the skill triggers a shift in strategy to question the underlying architecture rather than continuing to treat symptoms.

How does this skill handle multi-layer systems?

It implements diagnostic instrumentation at component boundaries to trace data flow, logging exactly what enters and exits each layer to identify the specific failing component.

When should I use the Systematic Debugging skill?

It should be used for any technical issue including test failures, production bugs, build errors, or whenever a 'simple' fix has already failed to solve the problem.

What is the primary rule of the Systematic Debugging skill?

The core 'Iron Law' is that no fixes should be proposed or implemented until a thorough root cause investigation is completed and the issue is consistently reproduced.

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

Yes, it specifically requires the creation of a failing test case in Phase 4 to verify the fix and ensure the bug does not regress in the future.

Systematic Debugging

Name: Systematic Debugging
Author: SkogAI

bySkogAI

•

セキュリティとテスト

Enforces a rigorous four-phase framework to identify root causes and implement stable fixes for any technical issue.

This skill provides a structured methodology to eliminate guesswork in software debugging by mandating a thorough root cause investigation before any fix is proposed. By guiding Claude through a sequence of investigation, pattern analysis, hypothesis testing, and implementation, it prevents the introduction of new bugs and ensures that even complex multi-component failures are resolved permanently. It is particularly effective for troubleshooting intermittent failures, architectural flaws, and performance regressions where random patching would otherwise lead to technical debt.

主な機能

01Mandatory root cause investigation phase before code changes

02Evidence-based pattern analysis and reference comparison

031 GitHub stars

04Diagnostic instrumentation for multi-component system boundaries

05Scientific hypothesis testing with minimal variable changes

06Architectural re-evaluation triggers after repeated fix failures

ユースケース

01Debugging intermittent CI/CD pipeline or build failures

02Resolving complex bugs in multi-layer API and database architectures

03Troubleshooting performance regressions and unexpected production behavior

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add skogai/skillsandknowledge systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill