Is a failing test case required for every bug fix?

Yes, the skill requires creating a failing test that reproduces the bug before implementing the fix to ensure the solution is verified and prevents future regressions.

What are the four phases of this debugging framework?

The workflow follows a logical progression: Collect Evidence, Isolate Variables, Formulate Hypotheses, and Test Hypothesis, followed by a final Verify Fix phase.

What happens if a hypothesis is proven wrong during testing?

The skill triggers an 'Iterate' task, looping back to the hypothesis formulation stage with new evidence, ensuring the agent doesn't get stuck on a single incorrect path.

How does this skill prevent 'guess-and-check' coding behavior?

It enforces an 'Iron Law' that strictly prohibits proposing solutions or changing code until a root cause has been identified through systematic evidence gathering and variable isolation.

Can this skill help with performance issues like memory leaks or high CPU usage?

Yes, the framework includes specific procedures for gathering evidence, analyzing patterns, and tracing data flows which are essential for diagnosing performance bottlenecks.

Systematic Debugging & Diagnosis

Name: Systematic Debugging & Diagnosis
Author: outfitter-dev

byoutfitter-dev

•

보안 및 테스팅

Implements a rigorous, evidence-based framework for identifying root causes and verifying fixes for software bugs and performance issues.

This skill equips Claude with a structured four-phase debugging framework designed to eliminate guesswork and trial-and-error fixes. By enforcing a strict policy of root-cause investigation before any code changes, it guides the agent through systematic evidence collection, variable isolation, hypothesis testing, and final verification. It is particularly effective for resolving complex intermittent failures, performance bottlenecks, and integration issues where the source of the problem is not immediately obvious, ensuring that every fix is backed by a passing test case and a deep understanding of the underlying error.

주요 기능

01Four-phase investigative framework (Evidence, Isolation, Hypothesis, Verification)

02Automated progress tracking via state-based phase transitions and todo lists

03Mandatory creation of failing test cases to reproduce and verify every bug

04Integrated circuit-breaker pattern to escalate complex or architectural failures

05Strict 'Iron Law' requiring root cause identification before proposing any code fixes

0616 GitHub stars

사용 사례

01Diagnosing intermittent race conditions or timing-dependent failures in asynchronous applications

02Root-cause analysis of production crashes with complex stack traces and deep dependency chains

03Resolving failing integration tests involving external APIs, databases, or third-party services

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add outfitter-dev/agents debugging-and-diagnosis

For use in Claude.ai and ChatGPT

Download Skill