Repository navigation
3.0.0
🚀 3.0.0 - Engine bridges and the Unity CLI
Agents can now reach the game editor through several bridges at once, including Unity's own command line. unikit-ai update moves 2.x projects to the new layout.
⚠️ Breaking Changes
- Engine MCP servers became engine bridges.
unikit-ai updatemoves them frommcp.serverstoengineBridges.selectedin.unikit.jsonand moves the findings logs to.unikit/bridge-notes/. It also rewrites## MCP Findingsin your plans but does not commit the change, so review that diff and commit it yourself. Until a 2.x project is updated,rules syncandrules installstop with exit code 8. - Three skills were renamed.
/unikit-mcp-trapis now/unikit-bridge-trap,/unikit-mcp-auditis now/unikit-bridge-auditand/unikit-devcontextis now/unikit-execute.updateinstalls the new names in place of the old ones. Two things are left to you: move.unikit/skill-context/unikit-devcontext/to.unikit/skill-context/unikit-execute/, and change studio rules whoseRequired Bynamesunikit-devcontextto nameunikit-execute. - Four template variables for extensions were replaced.
{{system_engine_mcp_dir}},{{engine_mcp_rules_index}},{{engine_mcp_rules_verification}}and{{engine_mcp_tool}}are no longer filled in. Use{{system_engine_bridges_dir}},{{engine_bridges_manifest}}and{{engine_bridge_mcp_code}}instead.
Upgrade guide: Migrating to 3.0.0
🧩 Engine Bridges
Pick any number of editor bridges, MCP servers or the Unity CLI, and agents try them in the order you set. A check that one bridge cannot do moves on to the next.
What's included
- Unity CLI bridge (Unity 6000.0+,
com.unity.pipelinepackage), checked by default on a fresh Unity setup;/unikitchecks the environment and asks before runningunity pipeline install - The order lives in
.unikit/bridges.yaml: edit it by hand or ask/unikit-bridge-route, and nothing gets reinstalled - New
/unikit-bridge-routesaves rules like "run tests only through the CLI" in.unikit/bridge-routing.md - Each bridge has its own findings file in
.unikit/bridge-notes/; when you drop a bridge its file is archived, and it comes back when you re-add the bridge initoffers optional registry rules for the selected MCP servers and bridges;updateasks before adding new ones and remembers what you declined
🏗 Architecture Topics
/unikit-architecture can split a large .unikit/ARCHITECTURE.md into a short root file and topic files in .unikit/architecture/. Skills then load only the topics that match the work at hand.
Details
updatemode rescans the project and adds what is missing, removing nothingoptimisemode moves the existing text into topics word for word, only after you confirm- Planning, implementation, checks and reviews pick topics by the task or the changed files
✨ Skills and Agents
Small tasks can now be done without a plan, and a project that is already set up gets a menu instead of the full setup again. To add the new skills to an existing project, run unikit-ai update --install-new.
What's included
/unikit-executedoes one task straight from its description, in code or in the editor, and checks that the code compiles/unikit-referenceskeeps your own documents and links for the agents in.unikit/references/, with an index- On a project that is already set up,
/unikitoffers four actions: add missing config keys, check the environment, create stack rules, or rescan and rewrite the project description /unikit-archivenow also archives and restores code researches, and plans still find a linked research after it is archived- Kimi Code can set subagent models per role (
subagents.model.kimi.<role>), using the template.kimi-code/kimi-subagent-models.toml, which you merge into your Kimi config by hand
🐛 Fixes
- Plan task fields (
WHY:,Files:,Editor:, …) are now separate paragraphs, so Markdown viewers no longer merge them into one line - Reviewers started by
/unikit-reviewnow use the subagent model and effort set in.unikit/config.yaml
Full Changelog: 2.5.0...3.0.0