unity-runlisted

# Run Unity CLI Execute Unity in batchmode from the command line. This skill handles finding the Unity installation and constructing the CLI command. Calling skills (tests, builds) provide the specific flags. ## Step 1: Find the Unity project Starting from the current working directory, locate `ProjectSettings/ProjectVersion.txt` by walking up or using Glob. The directory containing `ProjectSettings/` is the project root. If the user provides a project path explicitly, use that instead. ## Step 2: Detect Unity installation Use the plugin's detection script: ```bash UNITY_PATH=$("${CLAUDE_PLUGIN_ROOT}/scripts/find-unity.sh" "<project-root>") ``` The script auto-detects Unity via Hub config, default paths, and Hub CLI fallback. It reads the project's `ProjectVersion.txt` to find the matching editor version. If detection fails, ask the user to set `UNITY_EDITOR_PATH` environment variable. ## Step 3: Build and run the command Construct the Unity CLI command with batchmode defaults: ```bash "$UNITY_PATH" -batchmode -projectPath "<project-root>" <caller-flags> -logFile - -quit ``` **Defaults (always include unless caller overrides):** - `-batchmode` — no GUI - `-projectPath` — the detected project root - `-logFile -` — stream log to stdout (use a file path if caller needs to parse logs separately) - `-quit` — exit after execution **Caller provides:** the purpose-specific flags (e.g., `-runTests`, `-buildTarget`, `-executeMethod`). **Timeout:** Set to 600000ms (10 min