Project Auditor Fixes

Using Project Auditor Project Auditor carries out a static analysis scan of the Unity Project and reports a list of CSV issues that may be fixed. Trigger, poll, read.

Prerequisites

To use Project Auditor you'll need the Unity CLI installed - see the unity-cli skill for more details. Once you have that, the diagnostics run_audit and diagnostics audit_status commands run Project Auditor checks.

unity command diagnostics run_audit              # optional: --categories Code,ProjectSetting --output my.csv
unity command diagnostics audit_status           # repeat until a terminal status is returned

diagnostics audit_status terminal status are completed (with csvPath + issueCount), failed, unavailable, and interrupted (a domain reload killed the scan, just re-run diagnostics run_audit). Polling is responsive while a scan compiles assemblies and is busy on the main thread. You can only run one scan at a time: a second diagnostics run_audit returns busy. There is no cancel, stop polling to abandon a scan.

The output CSV has columns: Category, Severity, Areas, Description, RelativePath, Line, DescriptorId, Recommendation (these are diagnostics only, so every row is something to fix; Recommendation says how to do it).

Requires Project Auditor plus its rules. unavailable means the Editor has no Project Auditor, or it has no analysis rules, in a built-in-module Editor the rules live in the separate com.unity.project-auditor-rules package (unity command package add --identifier com.unity.project-auditor-rules --confirm true). Read the message field; the command never reports an empty completed scan that would look like a clean project.

Gotchas