domains / families / software-engineering / unity-cli

unity-cli

combined

Guide for using the experimental Unity CLI with bound UnitySkills projects Controls the Unity Editor and projects from the command line, driving a running Editor to edit scenes and assets or run C#. Use when asked to install or manage Editors, licenses, or projects, set up version control, build, test, configure the Unity MCP server, or run any unity command.

When to use

• Cold start Unity editor
• Check editor status
• Run preflight checks
• Verify project integrity
• Run CLI tests
• Run CLI builds
• Diagnose CLI environment

When not to use

• Use when cli_config.json is missing or disabled
• Install Unity editor
• Hand-repair project errors
• Modify server or config to work around CLI quirks
• Use registry.json for authorization

Skill page

Conflict

The two copies describe different, non-interchangeable procedures for the same skill name. The Unity-Technologies copy is the upstream CLI skill: it drives a running Editor via the Pipeline package, covers installation, global flags, and live command execution. The Besty0728 copy is a community 'advisory' wrapper that gates all CLI use behind a project-specific cli_config.json, treats the CLI as experimental/beta, and focuses on cold-starting the Editor and preflight checks. Neither copy contains the other's core authorization model or primary workflow, so crowning one would hide a real alternative.