domains / families / software-engineering / debug

debug

combined

Inspect debug, diagnostics and compile state Systematic debugging with persistent state across context resets

When to use

• Diagnosing compile failures
• Checking errors after a change
• Forcing recompilation
• Gathering system diagnostics
• Systematic debugging with persistent state
• Diagnose only without applying a fix

When not to use

• Runtime console logs
• Play mode control
• Script compile feedback

Skill page

Conflict

The three copies are not reproductions of one procedure. The first is a Unity-specific API reference for a set of debug skills (unity_diagnose, debug_get_errors, etc.) with parameters and routing rules. The second is a GSD-specific orchestrator that manages persistent debug sessions via subagents and file state. The third is a general-purpose, language-agnostic debugging methodology (reproduce, localize, hypothesize, test, fix, verify). They overlap only in the broad goal of debugging, but each contains material steps and constraints the others lack, so crowning one would hide real alternatives.