What happens if three or more fix attempts fail?

The protocol mandates a stop to all coding and triggers an architectural review, as repeated failures usually indicate a fundamental design flaw rather than a simple logic error.

When is the best time to trigger the systematic debugging protocol?

You should use it for any technical issue, especially when under time pressure, when a 'simple' fix has already failed, or when dealing with complex integrations.

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

The core principle of this skill is that quick patches often mask symptoms without solving the underlying problem. It enforces a 'Root Cause First' rule to prevent technical debt and bug recurrence.

Does this skill help with test-driven development?

Yes, Phase 4 of the process requires creating a minimal failing test case before any fix is implemented, ensuring the solution is verified and future-proof.

How does the skill handle bugs in multi-component systems?

It implements diagnostic instrumentation at every component boundary (e.g., API to Database) to log entering and exiting data, pinpointing exactly where the failure occurs.

Systematic Debugging

Name: Systematic Debugging
Author: claudiodearaujo

byclaudiodearaujo

보안 및 테스팅

Enforces a rigorous four-phase protocol to identify root causes and implement verified fixes for complex software bugs.

소개

Systematic Debugging provides a structured framework for resolving technical issues by mandating a root-cause-first approach. It moves developers away from inefficient 'guess-and-check' workflows by requiring evidence gathering, pattern analysis, and minimal hypothesis testing before any production code is altered. This skill is particularly effective for multi-component systems, elusive test failures, and deep architectural issues where quick patches often fail, ensuring that fixes are permanent and do not introduce regressions.

주요 기능

0 GitHub stars
Strict hypothesis testing methodology to verify assumptions with minimal code changes
Pattern analysis tools to compare failing code against known working reference implementations
Mandatory root cause investigation phase before any code modification is permitted
Diagnostic instrumentation for tracing data flow across complex multi-component boundaries
Architectural red-flag detection to identify when systemic refactoring is required over simple fixes

사용 사례

Identifying the source of intermittent or non-deterministic test failures in CI/CD pipelines
Tracing data corruption or state issues through multiple microservices and API layers
Resolving recurring 'voodoo' bugs where previous superficial fix attempts have consistently failed

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/izacenter systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill

GitHub

소개