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

If three or more fixes fail, the skill stops the cycle and initiates an architectural review to determine if the issue is a fundamental design flaw rather than a simple bug.

How does this skill handle multi-component system failures?

It implements diagnostic instrumentation at every component boundary to log data entry and exit, allowing Claude to isolate exactly which layer or service is failing.

When should I use the Systematic Debugging skill?

Use it for any technical issue, including test failures, production bugs, and performance problems, especially when under time pressure or when previous fix attempts have failed.

What is the 'Iron Law' of this debugging skill?

The Iron Law dictates that no fixes can be proposed or implemented until a thorough root cause investigation (Phase 1) is completed and the 'why' behind the bug is fully understood.

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

Yes, Phase 4 of the process requires creating a minimal failing test case to prove the bug exists before any fix is applied and verified.

Systematic Debugging

Name: Systematic Debugging
Author: KyteApp

byKyteApp

0•

安全与测试

Implements a rigorous four-phase methodology to identify root causes and resolve technical issues without introducing regressions.

The Systematic Debugging skill transforms Claude into a disciplined engineer that prioritizes deep root cause analysis over superficial 'guess-and-check' patches. By enforcing a strict workflow—comprising thorough investigation, pattern analysis, scientific hypothesis testing, and test-driven implementation—it prevents the common pitfalls of quick fixes that mask underlying architectural flaws. This skill is particularly effective for complex, multi-component systems where data flow is obscured, ensuring every resolution is backed by evidence and verified through failing test cases before completion.

主要功能

01Integration with Test-Driven Development for verified bug resolution

020 GitHub stars

03Backward data flow tracing to identify original error triggers

04Architectural questioning triggers after three failed fix attempts

05Diagnostic instrumentation for multi-layer systems and component boundaries

06Enforced 4-phase workflow: Root Cause, Pattern Analysis, Hypothesis, and Implementation

使用场景

01Resolving intermittent production bugs that lack consistent reproduction steps

02Identifying root causes in complex multi-component systems (CI to Build to Database)

03Breaking cycles of 'thrashing' where new fixes accidentally introduce regressions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add kyteapp/growth-agents-and-skills systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill