← ClaudeAtlas

unity-debuglisted

Verify a change in the running game: Editor.log, screenshots, tests; exit 0 but nothing ran.
tipoLi5890/unity-dev-skills · ★ 2 · Code & Development · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-debug — verify it yourself, and check the instrument first The agent cannot see the Game view. **Never iterate via "add a log → ask for a screenshot → guess".** Unity will run itself, report to a log, and hand you PNGs you can read. There is one rule above all the technique, and it is the one that costs the most when broken: > **A number is worthless until you know the run that produced it happened.** > Exit code 0 does not mean Unity started. A results file does not mean it is *this* run's results > file. A measurement does not mean the thing measured moved. A stale results XML reads "6/6 passed" while Unity fails to start on every run. Start at `reference/harness-trust.md`; the guard is one line of `rm`. ## Symptom → where to look | The report | Go to | |---|---| | "exit 0 but no results file", a run that did nothing, "the tests are green but nothing was verified" | `reference/harness-trust.md` | | "which test failed", `failed=0` that checked nothing | `reference/test-verdicts.md` | | "verify the fix works" in the running game | *The four loops* | | "the player won't move", "nothing happens when I press Play" | `reference/log-triage.md`, then `reference/editor-control.md` | | "the UI is shaking / flickering", anything temporal | `reference/motion-and-timing.md`, `reference/visual-checks.md` | | Green in the Editor, broken in a build | `reference/player-tests.md` | | Only breaks on the phone | skill `unity-device-testing` | | Anything else | *Load what the situ