What happens if multiple fix attempts fail?

If three or more fixes fail, the skill signals an architectural red flag, prompting you to question the underlying design rather than continuing to treat symptoms.

When should I use the Systematic Debugging skill?

Use it for any technical issue including test failures, production bugs, and performance problems, especially when simple fixes have already failed or the system is complex.

How does this skill handle multi-component systems?

It implements diagnostic instrumentation at every component boundary to log data entry and exit, allowing you to isolate exactly which layer of the system is failing.

What is the 'Iron Law' of systematic debugging?

The Iron Law states that no fixes should be proposed or implemented until a root cause investigation has been fully completed and the error is clearly understood.

Does this skill work with Test-Driven Development (TDD)?

Yes, the implementation phase specifically requires creating a failing test case to reproduce the bug before applying the fix, ensuring the solution is verified.

Systematic Debugging

Name: Systematic Debugging
Author: fzymgc-house

byfzymgc-house

0•

Seguridad y Pruebas

Implements a rigorous, four-phase debugging methodology to identify root causes and eliminate trial-and-error fixes.

This skill transforms how Claude handles troubleshooting by enforcing a strict 'no fixes without root cause' policy. It guides the AI through a structured workflow—investigation, pattern analysis, hypothesis testing, and implementation—to ensure bugs are permanently resolved rather than masked by temporary patches. It is particularly effective for complex, multi-layered systems where issues might be deep in the call stack or environment-specific, helping developers avoid the trap of random fixes that lead to architectural thrashing and technical debt.

Características Principales

01Utilizes a structured four-phase workflow to prevent inefficient guess-and-check thrashing.

02Automatically identifies architectural red flags when three or more fix attempts fail.

03Provides multi-layer diagnostic instrumentation for complex distributed and CI/CD systems.

04Enforces a strict 'Iron Law' of root cause investigation before any code changes are proposed.

05Integrates with test-driven development to ensure every fix is verified with a failing test case.

060 GitHub stars

Casos de Uso

01Investigating deep data flow errors in multi-component microservices or legacy codebases.

02Debugging complex CI/CD pipeline failures that involve multiple secret and environment handoffs.

03Resolving intermittent or non-reproducible bugs in production and staging environments.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add fzymgc-house/fzymgc-house-skills systematic-debugging

For use in Claude.ai and ChatGPT

Características Principales

01Utilizes a structured four-phase workflow to prevent inefficient guess-and-check thrashing.

02Automatically identifies architectural red flags when three or more fix attempts fail.

03Provides multi-layer diagnostic instrumentation for complex distributed and CI/CD systems.

04Enforces a strict 'Iron Law' of root cause investigation before any code changes are proposed.

05Integrates with test-driven development to ensure every fix is verified with a failing test case.

060 GitHub stars

Casos de Uso

01Investigating deep data flow errors in multi-component microservices or legacy codebases.

02Debugging complex CI/CD pipeline failures that involve multiple secret and environment handoffs.

03Resolving intermittent or non-reproducible bugs in production and staging environments.