foxctl Unity

What problem does it solve?

Managing a Unity project usually requires opening the editor to build/test, edit build scene order, tweak UPM dependencies, and configure the new Input System files, which slows down CI and automation workflows.

Core Features & Use Cases

• Build/test/export/clean Unity projects: Run Unity Editor CLI operations like building Standalone targets, exporting builds, running tests, and cleaning artifacts from the command line.
• Manage UPM dependencies: Add, remove, list, and query Unity package versions by editing Packages/manifest.json through declarative operations.
• Manage scene build settings: List scenes, add scenes, enable/disable scenes, reorder entries, and find scene files by updating ProjectSettings/EditorBuildSettings.asset.
• Manage Input System action maps: List action maps and actions, add maps/actions/bindings, and remove maps/actions inside Unity .inputactions assets.

Use case: Set up a repeatable CI workflow that verifies UPM packages, ensures the correct scene order for release, updates Input System bindings, and produces a deterministic build artifact for a target platform.

Quick Start

Use the foxctl Unity skill to build a Standalone player export for your selected target platform.