Why should I use this instead of letting Claude fix the bug immediately?

Immediate fixes often mask underlying symptoms and create regressions. This skill ensures the actual root cause is identified and resolved permanently, saving time on rework.

Does it work with existing testing frameworks?

Absolutely. It emphasizes creating automated failing test cases using your project's current tools to verify the fix before the task is considered complete.

When does the skill trigger an architectural review?

If three or more fix attempts fail, the framework flags a potential architectural flaw, prompting a discussion with the human partner rather than continuing to patch symptoms.

Can this help with intermittent or flaky tests?

Yes, it includes specific protocols for consistent reproduction and multi-layer evidence gathering to isolate issues that don't happen every time.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: AhmedElhadarey

byAhmedElhadarey

•

Security & Testing

Enforces a rigorous, four-phase scientific method to identify root causes and resolve technical issues without introducing regressions.

The Systematic Debugging skill provides a structured workflow for Claude to handle complex technical issues, ranging from flaky test failures to production bugs. By mandating a 'no fix without root cause' policy, it prevents the common pitfall of patching symptoms, which often leads to technical debt. The framework guides the AI through comprehensive evidence gathering, pattern analysis, and hypothesis testing, ensuring that every proposed solution is data-driven and verified through minimal testing before full implementation. It is particularly effective for multi-component systems where data flow is obscured across different layers.

Key Features

01Integrated Test-Driven Development (TDD) workflow for verifying resolutions.

02Multi-component diagnostic instrumentation for tracing errors across system boundaries.

03Architectural health checks that trigger after three failed fix attempts to prevent thrashing.

04Pattern analysis modules to compare broken code against working reference implementations.

052 GitHub stars

06Strict 'Root Cause First' investigation protocol to prevent symptom-only patching.

Use Cases

01Debugging deep-stack data flow issues in microservices or multi-layered software architectures.

02Resolving persistent bugs where previous 'quick fix' attempts have failed or caused regressions.

03Investigating intermittent failures in CI/CD pipelines or complex build environments.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ahmedelhadarey/gilfoyle systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill