Systematic Code Debugging FAQs

Question 1

What is the Iron Law of this debugging skill?

Accepted Answer

The Iron Law mandates that no fixes should be proposed or implemented until a thorough Phase 1 Root Cause Investigation is completed to ensure the source of the problem is understood.

Question 2

How does this skill handle bugs that are hard to reproduce?

Accepted Answer

It guides the user through gathering diagnostic data, checking recent git diffs, and adding instrumentation at component boundaries to gather evidence where the system breaks.

Question 3

Can this skill be used for build failures or performance issues?

Accepted Answer

Yes, the systematic approach is designed for any technical issue, including performance bottlenecks, build failures, and unexpected environment-specific behavior.

Question 4

What happens if a bug isn't fixed after three attempts?

Accepted Answer

The skill invokes a mandatory stop to question the fundamental architecture, as repeated failures often indicate an underlying problem with shared state or system coupling rather than a simple bug.

Question 5

Does this skill help with writing tests?

Accepted Answer

Yes, Phase 4 of the process requires creating a minimal failing test case to reproduce the bug before a single fix is implemented, ensuring the solution is verified and prevents regressions.

Systematic Code Debugging

主要功能

使用场景

Systematic Code Debugging

主要功能

使用场景