unity-build-commander

Execute headless Unity builds and parse Editor.log for compilation errors.

71|11|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nlelouche/Unity-SkillForge --skill unity-build-commander
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-build-commander
Source: https://github.com/nlelouche/Unity-SkillForge/tree/main/.agent/skills/09-devops-automation/unity-build-commander
Command: npx skills add https://github.com/nlelouche/Unity-SkillForge --skill unity-build-commander

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of building Unity projects for various platforms and immediately checks for compilation errors, allowing for rapid verification of code changes.

Core Features & Use Cases

  • Headless Builds: Executes Unity builds via the command line without opening the editor GUI.
  • Error Parsing: Analyzes the Editor.log to identify and report specific compilation errors.
  • Status Reporting: Provides a clear success or failure report of the build process.
  • Use Case: After making changes to game scripts, use this Skill to ensure the project still compiles correctly for the target platform before committing.

Quick Start

Use the unity-build-commander skill to build the project for Windows.

Frequently Asked Questions about unity-build-commander

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Unity builds and check for compilation errors?

To automate Unity builds, you can execute a headless command line build which compiles the project for a target platform and parses Editor.log to report specific compiler errors if the build fails.

Can I verify code changes in Unity for a specific target platform?

Yes, verifying code changes for a target platform involves running a headless Unity build that automatically checks the compilation status and lists any specific compiler errors encountered during the process.

How do I run a headless Unity build for CI/CD pipelines?

Running a headless Unity build for CI/CD pipelines involves executing the project compilation via the command line without the editor GUI, then analyzing Editor.log to report the build status and any failures.

What is the best way to check Unity compilation status before committing code?

The best way to check Unity compilation status before committing is to trigger a headless build that parses Editor.log to identify and report specific compilation errors, ensuring your project still compiles correctly.

Does this Unity build automation work without opening the editor GUI?

Yes, this Unity build automation works without opening the editor GUI by executing headless builds via the command line, allowing for rapid verification of code changes in automated environments.