How does this skill handle multi-component systems?

It implements diagnostic instrumentation at every component boundary, logging data entry/exit and environment state to pinpoint exactly where the failure occurs.

Why does this skill forbid fixes before investigation?

Fixing symptoms without finding the root cause often leads to regression bugs and masked issues. A systematic approach ensures the actual problem is solved permanently.

Is this debugging process slower than manual fixing?

While it requires more initial analysis, it is significantly faster in the long run by reducing 'thrashing' and the introduction of new bugs.

What happens if multiple fix attempts fail?

If three or more fixes fail, the skill mandates an architectural review to determine if the underlying pattern is fundamentally flawed rather than just buggy.

Systematic Debugging Framework

Name: Systematic Debugging Framework
Author: Krosebrook

byKrosebrook

•

Developer Tools

Implements a rigorous four-phase framework to identify root causes and resolve technical issues without guesswork or regressions.

The Systematic Debugging skill provides Claude with a disciplined methodology for troubleshooting software defects, preventing the inefficient 'guess-and-check' cycle that often leads to technical debt. By enforcing a mandatory root cause investigation phase before any code changes are proposed, this skill ensures that bugs are understood at a fundamental level across multi-component systems. It guides the AI through structured evidence gathering, pattern analysis, and minimal hypothesis testing, leading to robust implementations validated by automated tests.

Key Features

01Identifies architectural red flags when repeated fix attempts fail to resolve an issue

021 GitHub stars

03Structured 4-phase workflow: Investigation, Pattern Analysis, Hypothesis, and Implementation

04Integrated Test-Driven Development (TDD) requirements for verifying all fixes

05Enforces a 'Root Cause First' rule to prevent superficial patches and mask symptoms

06Provides diagnostic instrumentation strategies for complex, multi-layer system boundaries

Use Cases

01Resolving intermittent test failures and race conditions in complex CI/CD pipelines

02Investigating 'mysterious' production bugs where previous quick-fix attempts have failed

03Troubleshooting data flow and state propagation issues in microservices and multi-component systems

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add krosebrook/source-of-truth-monorepo systematic-debugging

For use in Claude.ai and ChatGPT

Download Skill