What if three fix attempts fail to solve the problem?

The process mandates an architectural review to determine if the issue is a fundamental design flaw rather than a code-level bug, preventing further wasted effort.

When should I use the Systematic Debugging skill?

Use it for any test failures, production bugs, performance regressions, or unexpected behavior, especially when under time pressure or after previous fixes have failed.

What happens if I can't reproduce the bug consistently?

The skill guides you to gather more diagnostic evidence, logs, and instrumentation instead of guessing, ensuring a data-driven approach to reproduction.

Why can't I just apply a quick fix?

Quick fixes often mask symptoms rather than solving the underlying issue, leading to technical debt and the high likelihood of introducing new bugs.

Does this skill work for multi-component systems?

Yes, it includes specific protocols for logging data at component boundaries (like API to Database) to isolate exactly where the data flow breaks down.

Systematic Debugging

Name: Systematic Debugging
Author: pur3v4d3r

bypur3v4d3r

•

보안 및 테스팅

Enforces a rigorous, evidence-based root cause analysis process before attempting any code fixes or patches.

This skill provides a structured four-phase framework for identifying and resolving technical issues, ensuring that Claude finds the actual root cause instead of applying superficial patches. By mandating evidence gathering, pattern analysis, and minimal hypothesis testing, it prevents 'guess-and-check' thrashing and reduces the introduction of new bugs. It is particularly effective for complex multi-component systems, intermittent failures, and scenarios where previous fix attempts have failed, providing a clear path from investigation to verified implementation.

주요 기능

01Scientific hypothesis testing using minimal, single-variable changes to isolate issues

02Architectural review trigger after three failed fix attempts to prevent technical thrashing

03Systematic pattern analysis comparing broken code against known-working references

04Multi-component diagnostic instrumentation for tracing data flow across system boundaries

05Mandatory root cause investigation phase before any code modifications are proposed

061 GitHub stars

사용 사례

01Investigating deep-stack logic errors in microservices or API integrations

02Resolving intermittent production bugs that require consistent reproduction steps

03Debugging complex CI/CD pipeline failures or multi-layered build scripts

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add pur3v4d3r/pur3-pkb-codebase systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill