Does this skill work with multi-component systems?

Yes, it includes specific steps for adding diagnostic instrumentation at system boundaries to trace data flow before proposing any changes.

How does this skill handle flaky tests?

It utilizes a specific checklist to analyze if failures are caused by environment variables, timing/timeouts, state pollution, or race conditions before investigating the core logic.

What happens if a bug requires more than three attempted fixes?

The skill triggers an 'Architectural Questioning' phase, prompting a discussion about whether the underlying system design or pattern is fundamentally unsound.

When should I use systematic debugging instead of a quick fix?

Use it for any technical issue where the root cause isn't immediately obvious, especially when previous fixes have failed or the issue involves multiple components.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: jrc1883

byjrc1883

•

Security & Testing

Resolves complex technical issues using a rigorous four-phase methodology focused on root-cause identification rather than quick fixes.

This skill provides Claude with a structured protocol for troubleshooting complex bugs, flaky tests, and multi-component failures. By enforcing the 'Iron Law' of no fixes without root cause investigation, it prevents the common pitfall of applying superficial patches that mask deeper issues. The skill guides the AI through systematic investigation, pattern analysis, hypothesis testing, and rigorous implementation verification, ensuring high-quality, long-term resolutions that reduce technical debt and prevent regression.

Key Features

01Architectural red-flag detection to identify when a system requires refactoring over patching

02Structured four-phase workflow: Root Cause, Pattern Analysis, Hypothesis, and Implementation

03Multi-component instrumentation strategies for tracing data flow across boundaries

04Integration with Test-Driven Development (TDD) for verified, permanent bug resolution

055 GitHub stars

06Flaky test diagnostic checklist to isolate timing, environment, and state-pollution issues

Use Cases

01Preventing 'fix-thrashing' where multiple attempted patches fail to resolve an underlying issue

02Identifying the root cause of race conditions and async errors in complex distributed systems

03Diagnosing intermittent 'flaky' test failures in CI/CD pipelines and local environments

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jrc1883/popkit-claude pop-systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill