build-verify

Lumina — Build & Verify

Turn "I wrote some code" into "it actually compiles and runs." This is the verifier half of the loop. Return structured, actionable errors so the orchestrator can self-correct.

Project path (default = current dir): $ARGUMENTS

Approach

Two complementary checks — do the cheap one first:

1. Compile check (fast). Trigger a script recompile and read the result.

   • Preferred: ask the engine MCP (mcp__unity) to recompile and return console errors — this is fastest because the Editor is already running.
   • Headless fallback (no Editor session): run the Unity CLI in batch mode:

     Unity -batchmode -quit -projectPath "<path>" -logFile -
     

     Capture stdout/stderr; the compile errors appear in the log.

2. Tests (if present). Run Unity Test Runner headlessly:

   Unity -batchmode -runTests -projectPath "<path>" -testPlatform PlayMode -testResults "<path>/TestResults.xml" -logFile -
   

   Also run -testPlatform EditMode if edit-mode tests exist. Parse TestResults.xml.

Output contract

Always return a compact, structured summary the orchestrator can act on:

RESULT: pass | fail
COMPILE:
  - <File.cs>:<line> <CSxxxx> <message>
TESTS: <n passed, m failed>
  - FAILED <TestName>: <assertion / message>
NEXT: <one-line hypothesis for the most likely root cause, if failed>

Rules

• Read the real log, don't guess. Use Read/Grep on the captured log and TestResults.xml.
• Surface the first root-cause compile error prominently — later errors are often cascades.
• Don't fix here — that's the orchestrator's job. Your job is an accurate verdict.
• Note when you fell back to the slow headless path (the Editor wasn't connected) so the user can keep the Editor open for a faster loop.