Run any Skill in Manus with one click

unity-check-script-assemblies

Stars0

Forks0

UpdatedMarch 12, 2026 at 21:01

Check whether a Unity project's C# scripts currently compile by rerunning the cached Bee `ScriptAssemblies` target from the latest Unity Editor DAG. Use when an agent needs a fast build verdict for Unity scripts, wants compiler errors without launching a full editor-driven build, or needs to confirm whether recent code changes introduced C# compilation failures in a Unity project.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

renanliberato

renanliberato/agent-tools

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

name	unity-check-script-assemblies
description	Check whether a Unity project's C# scripts currently compile by rerunning the cached Bee `ScriptAssemblies` target from the latest Unity Editor DAG. Use when an agent needs a fast build verdict for Unity scripts, wants compiler errors without launching a full editor-driven build, or needs to confirm whether recent code changes introduced C# compilation failures in a Unity project.

Unity Check Script Assemblies

Workflow

Confirm the project is a Unity project. Run this skill from a project root that contains ProjectSettings/ProjectVersion.txt.
Ensure Unity has produced a recent DAG for this project. This workflow depends on the latest ScriptAssemblies DAG entry in ~/Library/Logs/Unity/Editor.log. If the script reports that no DAG was found, open the project in Unity or trigger a compile once, then rerun the skill.
Run the helper script from the Unity project root.

/Users/renan.liberato/.codex/skills/unity-check-script-assemblies/scripts/check_script_assemblies.sh

To target a different project root explicitly:

/Users/renan.liberato/.codex/skills/unity-check-script-assemblies/scripts/check_script_assemblies.sh /path/to/unity-project

Interpret the result directly from the command output. A successful compile ends with *** Tundra build success .... A failed compile ends with *** Tundra build failed ... and includes Roslyn or Bee error details such as file paths, line numbers, and compiler error codes.
Report the result succinctly. State whether ScriptAssemblies built successfully. If the build failed, include the first actionable compiler error with its file and line number.

Practical Notes

Prefer this skill when the user wants a quick compile verdict instead of a full Unity test run or editor launch workflow.
The helper script resolves bee_backend from both supported Unity layouts: Unity.app/Contents/bee_backend (Unity 6.2) and Unity.app/Contents/Resources/BuildPipeline/bee_backend (Unity 6.3).
Treat missing ProjectVersion.txt, a missing Unity installation for that version, or a missing DAG entry as setup/precondition failures, not compile failures.
Do not hide the raw compiler output. Summarize it, but preserve the important failing path, line, and error code in your response.
If multiple Unity projects have been opened recently and the DAG looks stale or unrelated, tell the user the Editor log may need to be refreshed by opening the target project in Unity and compiling once.

More from this repository

same repository

kanban-commit

renanliberato/agent-tools

Commit task changes from a worktree onto the base branch (read from KANBAN_BASE_BRANCH env var). Use when finishing a kanban task to stage, commit, and cherry-pick changes back to the base ref.

2026-04-300

kanban-orphan-commit-recovery

renanliberato/agent-tools

Recover orphaned/dangling commits from kanban headless runs where the AI agent committed in the worktree but the kanban-commit agent failed to cherry-pick to the target branch (commit exists as a dangling object unreachable from any ref). Use when a ai-task-start-kanban-headless run completed/finished but the commit is missing from the target branch, or when investigating "nothing to commit — working tree is clean" in kanban-commit agent output.

2026-04-300

backlog-add

renanliberato/agent-tools

Capture a new feature, bug, or tweak idea as an issue file in the project's kanban repo at <project>-kanban/issues/<id>-<slug>.backlog.md. Runs a short grilling pass against the existing domain model so the entry is sharper than a one-liner. Uses sequential IDs (via flock(1)) so files sort naturally even with concurrent agents.

2026-04-300

git-history-improve

renanliberato/agent-tools

Plan and execute a full git history squash job — analyze commits between two refs, group them into ~10 semantically meaningful squashes, drop irrelevant directories or paths, cherry-pick each group with conflict resolution onto a new branch, and verify the final tree matches the original modulo dropped paths. Use when the user says "reduce commits", "squash branch history", "clean up git history", "rewrite branch", "compress commits", or wants to consolidate a messy branch before merge.

2026-04-300

backlog-promote

renanliberato/agent-tools

DEPRECATED — The backlog/issue distinction no longer exists. All work items are issues (<project>-kanban/issues/<id>-<slug>.<state>.md) from creation. Use backlog-add to capture an issue, to-prd to create a PRD. This skill is kept for reference only.

2026-04-300

session-to-backlog

renanliberato/agent-tools

Read the last pi agent session for the current project, extract what was discussed or done, and create issue files (as <project>-kanban/issues/<id>-<slug>.backlog.md) for any work items, bugs, or follow-ups it uncovered. Use when a session ended without wrapping everything up, when the user wants to capture session outcomes, or when you need to preserve context across sessions.

2026-04-300

name	unity-check-script-assemblies
description	Check whether a Unity project's C# scripts currently compile by rerunning the cached Bee `ScriptAssemblies` target from the latest Unity Editor DAG. Use when an agent needs a fast build verdict for Unity scripts, wants compiler errors without launching a full editor-driven build, or needs to confirm whether recent code changes introduced C# compilation failures in a Unity project.

Unity Check Script Assemblies

Workflow

Confirm the project is a Unity project. Run this skill from a project root that contains ProjectSettings/ProjectVersion.txt.
Ensure Unity has produced a recent DAG for this project. This workflow depends on the latest ScriptAssemblies DAG entry in ~/Library/Logs/Unity/Editor.log. If the script reports that no DAG was found, open the project in Unity or trigger a compile once, then rerun the skill.
Run the helper script from the Unity project root.

/Users/renan.liberato/.codex/skills/unity-check-script-assemblies/scripts/check_script_assemblies.sh

To target a different project root explicitly:

/Users/renan.liberato/.codex/skills/unity-check-script-assemblies/scripts/check_script_assemblies.sh /path/to/unity-project

Interpret the result directly from the command output. A successful compile ends with *** Tundra build success .... A failed compile ends with *** Tundra build failed ... and includes Roslyn or Bee error details such as file paths, line numbers, and compiler error codes.
Report the result succinctly. State whether ScriptAssemblies built successfully. If the build failed, include the first actionable compiler error with its file and line number.

Practical Notes

Prefer this skill when the user wants a quick compile verdict instead of a full Unity test run or editor launch workflow.
The helper script resolves bee_backend from both supported Unity layouts: Unity.app/Contents/bee_backend (Unity 6.2) and Unity.app/Contents/Resources/BuildPipeline/bee_backend (Unity 6.3).
Treat missing ProjectVersion.txt, a missing Unity installation for that version, or a missing DAG entry as setup/precondition failures, not compile failures.
Do not hide the raw compiler output. Summarize it, but preserve the important failing path, line, and error code in your response.
If multiple Unity projects have been opened recently and the DAG looks stale or unrelated, tell the user the Editor log may need to be refreshed by opening the target project in Unity and compiling once.