Hello Unity dev community!
I’m happy to announce a tool that improves our team’s VCS asset workflow and saves time when reviewing and merging asset changes.
MergeSight is a Unity Editor extension and standalone CLI for semantic review, 3-way merge, automation, and CI workflows for text-serialized Unity assets.
It helps teams cut review time and resolve merge conflicts by turning raw YAML diffs into a Unity-aware view of objects, components, hierarchy, properties, and references.
The workflow covers scenes, prefabs, ScriptableObjects, materials, and other YAML-based Unity assets in Git, Perforce, Unity Version Control / Plastic SCM, or SVN.
The CLI supports CI checks, merge-driver workflows, validation runs, and external VCS integration.
Semantic Review
MergeSight converts Unity YAML diffs into a semantic tree of object-level and property-level changes.
This view makes it easier to inspect what changed in Unity terms: GameObjects, components, hierarchy updates, serialized properties, and references. It is useful for branch comparison, working tree review, and pull request review.
Version Compare
MergeSight compares different versions of Unity assets across branches, commits, and working tree states.
This makes it easier to inspect changes before they become merge problems, and to review asset history in the same Unity-oriented model used by the rest of the tool.
Filter Assets and Changes
MergeSight lets you narrow large reviews down to the files and change types that matter.
You can filter changed assets by type, path, name, and Git/VCS status, then filter the semantic diff tree by search query, change kind, and item type such as objects, components, or properties. This is useful when a single revision touches many assets and only a few of them need close inspection.
3-Way Merge Workflow
MergeSight provides a structured BASE / OURS / THEIRS merge view for conflicted Unity assets.
Each conflict stays visible in context, and the user chooses the correct side or applies a safe merge action where appropriate. The merge flow is designed for Unity data structures that involve object ownership, hierarchy changes, component attachments, local references, and serialized fields.
Conflict Preview and Safe Apply
MergeSight shows the composed result before writing the final asset.
Apply is blocked while unresolved decisions remain. The tool creates a backup before writing results and fails closed on ambiguous or unsupported structures. That keeps the merge path predictable for interactive use and automation.
Unity-Aware Structure
MergeSight understands Unity asset structure directly.
Supported structure includes:
- GameObject and component ownership
- parent/child hierarchy relationships
- scene root ordering
- local references and object IDs
- material saved-property paths
- ScriptableObject and generic
.assetcontent
This keeps review and merge decisions aligned with Unity’s data model, which makes the output easier to trust than a line-based text diff.
References, GUIDs, and Unity Serialization
MergeSight also handles the Unity-specific reference model that appears throughout serialized assets.
This includes:
- GUID-based asset references
- local
fileIDreferences inside a file - object fields that point to external assets
- object fields that point to sub-assets or scene objects
- serialized Unity structures that depend on stable ownership and reference resolution
This part matters when a diff looks small in text but changes how Unity resolves an asset graph. Seeing references and object relationships in context makes review and merge decisions much easier to trust.
Supported Asset Types
Primary support:
.unity.prefab.asset.mat
The tooling is built around Unity text serialization, where diffs become noisy quickly and semantic review provides the most value.
VCS, Automation, and CLI Workflows
MergeSight ships with an interactive Editor workflow and a standalone CLI library.
The Editor handles review and merge operations.
The CLI handles automation, including CI checks, merge-driver workflows, validation runs, and external VCS integration points.
Supported workflows include Git, Perforce, Unity Version Control / Plastic SCM, and SVN.
Thank you for attention!
If this looks useful, you can join the whitelist on the product website to get release notification.
MergeSight will be available on the Asset Store later this month.