What problem does it solve?
Unity debugging often stalls when the cause is split across compilation issues, missing references, runtime log errors, and unclear scene state; this skill consolidates the evidence-gathering workflow so investigations start with the most reliable signals.
Core Features & Use Cases
- Investigation priority workflow: Starts with workspace knowledge and CRG tracing before moving to REST-based evidence, reducing wasted calls and incorrect assumptions.
- Aggregated Unity diagnostic snapshot (read-only): Performs an initial health check using a single REST call to quickly reveal compilation/play-mode/scene error signals.
- Targeted evidence modules: Collects compilation diagnostics, captured logs, scene structure, performance snapshots, and validation findings for missing scripts/references and shader/scene/project hygiene.
- ECS-aware guidance: Provides explicit investigation notes for how to proceed when ECS runtime state is not directly inspectable via REST.
Use cases: debugging compile-time failures, resolving NullReferenceException-like symptoms from missing scripts/assets, diagnosing scene/authoring problems, and capturing profiler-style performance evidence for regression analysis.
Quick Start
Run the unity-investigation skill to diagnose a Unity issue by first retrieving the aggregated health snapshot, then checking compilation diagnostics, and only afterward collecting targeted logs, scene evidence, or validation results as needed.
