What is the 'Iron Law' of Systematic Debugging?

The Iron Law states: 'NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.' This prevents developers from applying 'band-aid' fixes that mask symptoms without resolving the underlying issue.

Can I use this for performance optimization?

Yes, the skill includes specific strategies for profiling execution, identifying algorithmic bottlenecks, and tracing slow network requests or database queries.

Does this skill work with any programming language?

Yes, it is a language-agnostic discipline focused on logic and methodology, though it provides specific implementation patterns for TypeScript, Python, and Go.

How does this skill handle trial-and-error approaches?

It identifies 'Red Flags' such as adding null checks without understanding why a value is null or restarting servers without identifying corrupted state, steering the developer back to a logical investigation.

What are the four phases of the debugging process?

The process consists of: 1. Trace Data Flow, 2. Identify Divergence, 3. Hypothesize Root Cause, and 4. Verify Fix.

Systematic Debugging

Name: Systematic Debugging
Author: MadAppGang

byMadAppGang

•

214

보안 및 테스팅

Enforces a rigorous, hypothesis-driven methodology to identify and resolve the root cause of software defects.

소개

The Systematic Debugging skill provides a disciplined framework for troubleshooting complex software issues, moving beyond trial-and-error 'guessing.' It mandates an 'Iron Law' of root cause investigation before any code changes are made. By guiding developers through a structured four-phase process—tracing data flow, identifying divergences, forming testable hypotheses, and verifying fixes—this skill ensures that bugs are permanently resolved rather than merely masked. It is particularly effective for resolving race conditions, data corruption, performance bottlenecks, and elusive environment-specific errors.

주요 기능

Hypothesis-Driven Troubleshooting Templates
Data Flow Tracing & Divergence Analysis
Four-Phase Debugging Process (Trace, Identify, Hypothesize, Verify)
Comprehensive Fix Verification Checklist
214 GitHub stars
Root Cause Investigation (Iron Law enforcement)

사용 사례

Investigating intermittent race conditions in asynchronous JavaScript or Go applications.
Tracing the source of data corruption across complex state management systems.
Identifying the root cause of 'undefined' or 'null' errors in deep object structures.

소개

주요 기능

Hypothesis-Driven Troubleshooting Templates
Data Flow Tracing & Divergence Analysis
Four-Phase Debugging Process (Trace, Identify, Hypothesize, Verify)
Comprehensive Fix Verification Checklist
214 GitHub stars
Root Cause Investigation (Iron Law enforcement)

사용 사례

Investigating intermittent race conditions in asynchronous JavaScript or Go applications.
Tracing the source of data corruption across complex state management systems.
Identifying the root cause of 'undefined' or 'null' errors in deep object structures.