unity-technologies/unity-version-control

Address the comments a reviewer left on a UVCS / Plastic SCM code review or merge request, as the code author: find the review on the workspace's branch, list the change requests, questions and comments still pending, plan their order, then fix, answer, discard or re-request under the user's direction, one check-in per change request. Use when the user says fix the review, address the review comments, apply the review changes, my review came back as rework required, answer the reviewer's question, discard a review comment, or re-request review. This is the author side — producing findings and publishing them is uvcs-code-review. All cm syntax comes from the uvcs-core skill — load it first.

Review UVCS / Plastic SCM changes as the reviewer and publish the findings as review comments: a branch through its merge request, a changeset or shelve through a code review, or the workspace's pending changes in chat. Use when the user says review my changes, review this branch, review changeset 42 or shelve 12, code review, open a merge request or pull request, request a review from someone, publish review comments, approve, LGTM, or set my status to rework required. Merges the project's own code-review-rules skill into its general review rules when the project has one. Performing the merge is uvcs-merge; fixing a review as its author is uvcs-address-review. All cm syntax comes from the uvcs-core skill — load it first.

Core knowledge for Unity Version Control (UVCS, formerly Plastic SCM) and its cm command line: how UVCS concepts differ from git, object specs (br:, cs:, lb:, sh:, serverpath:), which cm command answers which question, read-only vs mutating vs irreversible commands, how to name UVCS objects and build deep links (plastic://, or unityhub:// when the workspace is a Unity project) when reporting results, and curated cm recipes for status, find queries, diff and patch, history, branches, checkin, shelves, merge requests and code reviews. Use whenever composing or running any cm command, or when the user mentions UVCS, Unity Version Control, Plastic SCM, cm, changeset, cset, workspace, selector, branch, label, shelve, shelveset, checkin, annotate, merge request, MR, pull request, PR, code review, reviewer, xlink, plastic:// or unityhub:// links. Every UVCS workflow skill builds on this one — load it first.

Merge a UVCS / Plastic SCM branch, changeset, label, or shelve into the current workspace with the cm CLI and drive it to a clean, resolved workspace without ever opening a merge tool window: preview first, apply with diff3 conflict markers, resolve or pick a contributor, verify, then hand the check-in decision back to the user. Use whenever the user wants to merge or integrate one UVCS branch into another, merge down from /main into a task branch, cherry-pick a changeset, resolve UVCS merge conflicts, finish a merge that is already in progress, or when cm refuses an operation because a merge is in progress or conflict markers are still pending. All cm syntax comes from the uvcs-core skill — load it first.

Report a defect or a gap in this UVCS agent plugin itself — a cm command or flag a skill gave that cm rejected, a fact a reference gets wrong, a recipe or workflow that is missing, a skill that did not trigger or behaved differently in another agent, or a result that was not what the user asked for — as a GitHub issue on the plugin's repository, with a redacted, reproducible scenario a maintainer can turn into a fix and an eval. Use when the user says report this bug, file an issue, the plugin or the skill got it wrong, request a skill or a workflow, or when uvcs-core flags a rejected recipe. Not for problems in UVCS, cm or a server themselves, and not for bugs in the user's own code.

Trace a bug, regression, crash or failing test back to the UVCS / Plastic SCM changeset that most likely introduced it: bound the history window, expand from the symptom file to what it depends on, rank only changesets with concrete evidence, and confirm the top suspect at line level with cm annotate. Read-only end to end. Use when the user asks why something broke, what changeset or cset broke it, which change introduced a bug, who broke a file or a line, when a feature last worked, how to bisect or blame a regression in UVCS, or hands you a stack trace, error message or failing test and wants the culprit changeset. Not for reviewing what a branch changed and not for performing a merge. All cm syntax comes from the uvcs-core skill — load it first.

Move a UVCS / Plastic SCM workspace onto another branch, changeset, label or shelve with cm switch — including creating the branch first — and handle pending changes the way the UVCS GUIs and the Unity plugin do: detect them, ask whether to leave them behind on a shelve or bring them along, then shelve, undo, switch, and reapply. Use whenever the user wants to switch, change or move the workspace to another UVCS branch, start a new task branch and work on it, or when cm switch is refused, cancelled or hangs because the workspace has pending changes. All cm syntax comes from the uvcs-core skill — load it first.