Audience: plugin maintainers. This audits whether the static built-in tables
in the unity-cli-command skill have drifted from the commands registered in the
running Editor (new actions added upstream, removed actions, changed signatures).
It does not touch the per-project custom-command cache — for that, use the
unity-cli-refresh-commands skill.
Running
cs: below,csis shorthand forpython "$HOME/.unity-cli-plugin/current/cli/cs.py"— one stable path, run verbatim without changing directory. If it's not installed yet, run the unity-cli-setup skill once first.
Steps:
- Fetch the live command list:
python "$HOME/.unity-cli-plugin/current/cli/cs.py" list-commands --json --project "$(pwd)"
-
Parse
data.commandsfrom the JSON output. This contains all registered commands (built-in + custom). -
Compare with the static catalog in the
unity-cli-commandskill'sSKILL.md. The built-in namespaces are: editor, gameobject, component, transform, material, prefab, project, scene, screenshot, profiler, session, command. -
Report differences:
- New commands not in SKILL.md → suggest adding them
- Removed commands in SKILL.md but not live → suggest removing them
- Changed signatures (different args) → suggest updating
-
If custom commands exist outside the built-in namespaces, also use the unity-cli-refresh-commands skill to update the custom command cache.