Terminal
Terminal/Skill
Runs Unity's Project Auditor static analysis on a project and works through the CSV issues it reports, fixing them in reviewable commits.
By Unity
Works with
npx skills add unity-technologies/skills --skill project-auditor-fixesUsing 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.
To use Project Auditor you'll need the Unity CLI installed - see the unity-cli skill for more details. Once you have that, the audit and audit_status commands run Project Auditor checks.
unity command audit # optional: --categories Code,ProjectSetting --output my.csv
unity command audit_status # repeat until a terminal status is returned
audit_status terminal status are completed (with csvPath + issueCount), failed, unavailable, and
interrupted (a domain reload killed the scan — just re-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 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.
unavailablemeans the Editor has no Project Auditor, or it has no analysis rules — in a built-in-module Editor the rules live in the separatecom.unity.project-auditor-rulespackage (unity command package_add --identifier com.unity.project-auditor-rules --confirm true). Read themessagefield; the command never reports an emptycompletedscan that would look like a clean project.
set_autotick first. Without it, recompile and tests can hang while the editor is
unfocused. The package's watchdog relies on the tick loop staying alive.reload_file_override / reload_file apply to a live
game — enter Editor Play Mode (unity command editor_play) first, or run a dev Player.log, set_timescale, runtime_status, etc. hit
the Runtime server, which does not run in the Editor.recompile→recompile_status, run_tests --async_tests→
test_status. Never assume completion from the trigger call's response.--instance host:port or --project-path <path>
when more than one is running.When fixing a list of issues it's best practice to have a test case to make sure things are still working correctly. This might be a particular scene to open and start play mode, or a particular platform to build and run. If this isn’t present and there are no instructions, suggest a test case to the user and ask for confirmation. Run the test case before and after changes to make sure the project is still working.
As you work, make sure any changes are committed in alignment with user version control setup. Wherever possible, commit step-by-step, breaking things down into changes that a user can easily understand.