When should I use the Systematic Debugging skill?

Apply this skill whenever you encounter test failures, production bugs, performance regressions, or any behavior that deviates from the expected technical requirements.

What happens if a fix attempt doesn't work?

The skill includes a safety protocol: if three fix attempts fail, it stops to question the underlying architecture and patterns rather than continuing to apply 'band-aid' solutions.

Does this skill work with complex, multi-component systems?

Yes, it includes specific strategies for adding diagnostic instrumentation at component boundaries (e.g., between a database and an API) to isolate exactly where a failure occurs.

Why does this skill prohibit immediate fixes?

Immediate fixes often mask symptoms rather than solving the underlying problem, leading to technical debt and recurring bugs. This skill ensures the root cause is verified before code is changed.

Systematic Debugging

Name: Systematic Debugging
Author: claudiodearaujo

byclaudiodearaujo

0•

安全与测试

Implements a rigorous four-phase methodology to identify root causes and resolve technical issues without trial-and-error thrashing.

The Systematic Debugging skill provides a structured framework for Claude to handle bugs, test failures, and unexpected behaviors by enforcing a strict root-cause-first protocol. It guides the AI through detailed evidence gathering, multi-component diagnostic instrumentation, and pattern analysis before any code changes are proposed. This approach prevents 'quick-fix' cycles that often mask underlying issues, ensuring that even complex architectural flaws are identified and addressed systematically rather than through guesswork.

主要功能

01Four-phase debugging framework (Root Cause, Pattern, Hypothesis, Implementation)

02Multi-component diagnostic instrumentation for complex system boundaries

03Backward data flow tracing and call-stack analysis techniques

04Architectural threshold alerts triggered after three failed fix attempts

05Seamless integration with Test-Driven Development (TDD) for fix verification

060 GitHub stars

使用场景

01Resolving intermittent CI/CD build failures or environment-specific configuration bugs.

02Debugging deep-seated data flow issues across multi-layered microservices or APIs.

03Eliminating 'fix-and-break' cycles during high-pressure production emergencies.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/izacenter systematic-debugging

For use in Claude.ai and ChatGPT

主要功能

01Four-phase debugging framework (Root Cause, Pattern, Hypothesis, Implementation)

02Multi-component diagnostic instrumentation for complex system boundaries

03Backward data flow tracing and call-stack analysis techniques

04Architectural threshold alerts triggered after three failed fix attempts

05Seamless integration with Test-Driven Development (TDD) for fix verification

060 GitHub stars

使用场景

01Resolving intermittent CI/CD build failures or environment-specific configuration bugs.

02Debugging deep-seated data flow issues across multi-layered microservices or APIs.

03Eliminating 'fix-and-break' cycles during high-pressure production emergencies.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/izacenter systematic-debugging

For use in Claude.ai and ChatGPT