Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Unity Version Control (Plastic SCM)

    1

    Lets your AI agent review branches, explain what changed between builds, preview merges, lock scenes and prefabs, and check in Unity assets with their .meta files in Plastic SCM / Unity Version Control, safely.

    Free

    Security scanned
    Unity Version Control (Plastic SCM)

    Unity Version Control (Plastic SCM)

    Example session with this skill installed

    Review the branch /main/player-dash before I merge it into /main.

    • Read your context and instructions
    • Compiled the unity version control

    Branch /main/player-dash: 3 changesets by alex ("Add dash ability"), 7 items changed.

    StatusItem
    changedAssets/Scripts/PlayerController.cs
    addedAssets/Scripts/DashAbility.cs + DashAbility.cs.meta
    changedAssets/Prefabs/Player.prefab
    addedAssets/Audio/dash.wav
    changedProjectSettings/InputManager.asset

    Warning: Assets/Audio/dash.wav was added without its .meta file. Unity will generate a new GUID, and references to this sound will break for the rest of the team. Add the .meta before merging.

    Key code change

    @@ -42,6 +42,9 @@
         void Update() {
             HandleMovement();
    +        if (Input.GetKeyDown(KeyCode.LeftShift) && dash.IsReady) {
    +            dash.Perform(transform.forward);
    +        }
         }
    

    Player.prefab is YAML text: the diff shows a new DashAbility component with cooldown: 1.5, but a line diff says little about the visual result. Check the prefab in the Editor.

    Merge preview into /main (computed on the server, nothing changed)

    • 6 files come from the branch
    • 1 conflict: Assets/Prefabs/Player.prefab was also changed on /main in cs:812

    Next steps

    1. Add Assets/Audio/dash.wav.meta on the branch.
    2. Merge in the UVCS client and resolve the prefab conflict there. The agent refuses merges with conflicts.
    3. After that, I can check in the merge result with a message that follows your naming rules.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Give Claude Code, Codex, Cursor, OpenCode, or Gemini CLI a safe, fluent way to work with Plastic SCM / Unity Version Control (UVCS). The skill teaches your agent which tool answers which question, how UVCS differs from Git, and the Unity rules that are easy to break.

    What your agent can do

    • Understand history: what changed in a changeset, on a branch, or between two build labels; line diffs of scripts, scenes, and prefabs; file history and per-line blame.
    • Review before merging: list a branch's changes, flag assets added or moved without their .meta, and preview a merge on the server to see conflicts without touching your workspace.
    • Lock shared assets: check whether a scene or prefab is locked, check it out (taking the exclusive lock when your server's lock.conf covers it), and release locks of files you did not change.
    • Check in exactly the right files: check in everything, or only the files of the current task. The .meta file of every selected asset comes along automatically, and an asset whose .meta is not added yet is refused.
    • Release work: branch, checkin, and label names that follow your team's conventions.

    Safe by design

    • Every write is two steps: the agent prepares the operation, shows it to you, and runs it only after you approve.
    • Read-only by default. Writes need the guarded profile, which pins the workspace and repository.
    • No shell and no raw cm: only a fixed set of commands. Merges with conflicts are refused, so they never stop half-done in your workspace.

    Requirements

    • The free, open-source uvcs MCP server (npx -y @proanima/uvcs-mcp init, MIT)
    • Node.js 22+
    • Unity Version Control / Plastic SCM cm CLI 10.0.16.6656 or newer (11.x included), logged in to your Cloud, on-premises, or local server

    Requires uvcs MCP server and Plastic SCM cm CLI 10.0.16.6656+. No support for manual conflict resolution or raw shell commands. Workspace must be pre-configured.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 22 days ago

    • Free with an Agensi account

    Requires

    Unity
    Node.js 22+
    Uvcs MCP
    Unity Version Control cm CLI
    Node.js
    @proanima/uvcs-mcp
    ENOENT

    Permissions

    Read Files
    Write Files
    Network Access

    Allowed Hosts

    unity.com

    File Scopes

    Assets/**
    Packages/**
    ProjectSettings/**
    .uvcs-mcp/style.json

    The skill only calls the tools of the uvcs MCP server; it never runs shell commands. Network access: the cm CLI talks to your Unity Version Control server, and npx downloads the MCP server from npm. File access is limited to the configured workspace: checkout, checkin, and undo change workspace files only after you approve each prepared operation. The server is read-only by default.

    Listed22 days ago

    What's inside

    Frequently Asked Questions

    Yes. Install the free uvcs MCP server (npx -y @proanima/uvcs-mcp init), plus Node.js 22+ and the Unity Version Control / Plastic SCM cm CLI 10.0.16.6656 or newer, logged in to your server.

    No. The server is read-only by default. Every write is two steps: the agent prepares the operation, shows it to you, and runs it only after you approve. There is no shell access and no raw cm.

    Yes. It uses your existing cm client configuration, so Unity Cloud, on-premises, and local servers all work.

    No. It previews merges and shows conflicts, and it refuses to start a merge that would stop with conflicts. Resolve those merges in the UVCS client.

    No. It works with source control only (history, review, locks, checkins, merges). It does not control scenes, Play Mode, or builds.

    New in Game Development