Diagnoses software root causes via structured 4-phase debugging methodology.
npx skills add https://github.com/afovea/game-dev-skills --skill diagnose-afovea
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/afovea/game-dev-skills/tree/main/plugins/game-team/skills/diagnose Command: npx skills add https://github.com/afovea/game-dev-skills --skill diagnose-afovea
This skill prevents symptom-only patching and guesswork by enforcing a rigorous, evidence-based debugging methodology that ensures fixes address the actual root cause of a failure.
Invoke the diagnose skill to begin a root cause investigation for the current rendering error in the project.
High-intent search queries and answers about installing and using this skill.
Systematic debugging of intermittent software bugs requires a structured 4-phase methodology that enforces evidence-based hypothesis testing to isolate root causes before applying code changes, preventing symptom-only patching and guesswork.
Finding the root cause of a state mutation error involves tracing failures from stack traces down to the underlying data source using a rigorous, evidence-based debugging methodology rather than applying temporary patches.
Designing minimal tests to prove a debugging hypothesis is the core of evidence-based troubleshooting, requiring you to validate or refute your root-cause diagnosis through targeted testing before implementing any actual code fixes.
Debugging processes often patch symptoms instead of fixing the actual failure because they lack an evidence-based methodology, bypassing the Iron Law of debugging which mandates proving a root cause before applying code changes.
You can use a systematic troubleshooting methodology for complex game engine errors by applying structured root cause investigation to isolate calculation issues, such as delta-time errors causing intermittent animation freezes, without temporary delays.
mtsatryanAnalyze error messages and stack traces to produce structured root-cause reports.
slabgorbGuide teams through a six-phase debugging workflow to identify root causes.
JylhisDiagnoses and fixes Go bugs using structured, evidence-based workflows and verification tools.
fanguyunDesign chaos experiments and implement failure injection frameworks for distributed systems.
