What problem does it solve? Developers often start editing code before reproducing a bug, which leads to fixing the wrong thing, shipping unverifiable changes, and letting silent bugs return. This Skill enforces a disciplined debugging order so every fix is grounded in a real reproduction and verified against regressions. ## Core Features & Use Cases - Strict four-step workflow: Repro → root cause → minimal fix → regression check, with no steps skipped. - Root-cause discipline: Inspect actual runtime values, serialized assets, subscriptions, and static state instead of reasoning about code in the abstract; check the checkpoint diff of the task that introduced the bug. - Scope guardrails: No drive-by refactoring, no silent mechanic changes, and clear rules for distinguishing bugs from balance tweaks or design changes. - Use Case: A user reports that units stutter after the last task. You reproduce the exact scenario, trace it to an unsubscribed event from the previous change, apply a minimal fix, rerun the repro, and add a line to the smoke-check list so the silent bug cannot return. ## Quick Start Use the bugfix skill to investigate why units stutter after the last task and produce a verified minimal fix.
