What is the 'Iron Law' of this skill?

The Iron Law states that no fixes should be proposed or implemented until a thorough root cause investigation (Phase 1) is completed and the error is fully understood.

What happens if three consecutive fix attempts fail?

The skill triggers an architectural review. Instead of attempting a fourth fix, it prompts the user to question the fundamental design and discuss the pattern with a human partner.

Can I use this for simple bugs or is it only for complex issues?

It is designed for both. While powerful for complex issues, applying the process to simple bugs ensures they are fixed correctly the first time and prevents them from resurfacing.

How does this skill handle multi-component systems?

It guides the user to add diagnostic instrumentation at every component boundary to log data flow, verifying environment propagation and identifying exactly which layer is failing.

Systematic Debugging

Name: Systematic Debugging
Author: Krosebrook

byKrosebrook

•

安全与测试

Eliminates software bugs by enforcing a rigorous, four-phase root cause analysis process before any code changes are made.

This skill provides a disciplined framework for troubleshooting complex software issues, preventing the common pitfall of 'guess-and-check' programming. By following a structured path—from evidence gathering and diagnostic instrumentation to pattern analysis and minimal hypothesis testing—it ensures that developers address the underlying source of errors rather than just masking symptoms. It is particularly effective for multi-component systems, intermittent failures, and situations where previous 'quick fixes' have failed, helping teams achieve a higher first-time fix rate and reduced technical debt.

主要功能

01Enforced four-phase investigation workflow to prevent premature fixing

02Backward data flow tracing techniques for deep-stack error identification

03Evidence-based reproduction protocols to eliminate guesswork

041 GitHub stars

05Multi-component diagnostic instrumentation for tracing data across boundaries

06Architectural health checks triggered after repeated fix failures

使用场景

01Debugging intermittent test failures in complex CI/CD pipelines

02Troubleshooting performance bottlenecks and environmental configuration mismatches

03Resolving production bugs where the data origin is obscured by multiple service layers

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