UVCS Prefab Review
How to Review Unity Prefab Changes in Unity Version Control
A useful UVCS prefab review should identify whether a changeset modified the prefab source, a nested prefab link, an instance override, component ownership, serialized properties, or object references. Review those concepts before accepting the changeset, not after a merge conflict exposes them.
Prepare the prefab for review
- Confirm the project uses Force Text serialization.
- Update the workspace so the comparison is based on current repository state.
- Identify the source and destination changesets or compare the workspace with its base.
- Include related prefab, material, ScriptableObject, script, and
.metachanges in the review scope. - Open the project in the same Unity version used to save the asset.
Review prefab changes in this order
- Object structure. Check added, removed, renamed, reparented, and reordered GameObjects.
- Components. Confirm component additions, removals, ownership, and serialized field changes.
- Nested prefab sources. Verify that each nested instance still points to the intended source asset.
- Overrides. Distinguish intentional instance customization from accidental override churn.
- References. Resolve GUID and fileID changes to the real assets and local objects.
- Validation. Open Prefab Mode, inspect missing scripts and references, then apply project tests.
Use a semantic diff for the difficult parts
UVCS can identify the changed file and provide revision content. A raw prefab YAML diff still forces the reviewer to reconstruct ownership and override context manually.
MergeSight UVCS prefab review can compare workspace or concrete changeset sources and show supported prefab changes as objects, components, properties, references, and prefab override data. Asset and diff-tree filters help isolate only overrides, references, or changed components.
Prefab review risk table
| Change | What to verify | Common failure |
|---|---|---|
| Nested source | Expected prefab GUID and source object | Instance silently points to a replacement asset. |
| Override path | Property target and intended local value | Override becomes stale or applies to a different target. |
| Component | Owner GameObject and script reference | Missing script or component attached to the wrong object. |
| Reorder | Child order and any order-dependent behavior | Large YAML churn hides a small but important move. |
| Reference | Resolved asset/object behind GUID and fileID | Valid YAML preserves a broken or unintended link. |
Acceptance checklist
- The prefab opens in Prefab Mode with no import or serialization errors.
- Intended nested prefab links and variant relationships remain intact.
- Overrides are deliberate, minimal, and target the expected properties.
- No missing scripts, dangling references, or component ownership errors remain.
- The UVCS changeset includes matching
.metafiles for moved or added assets. - The review note explains high-impact structure or reference changes in plain language.
FAQ
Can Unity Version Control show prefab changes?
Yes. UVCS can compare workspace revisions and changesets. For deeper review, use a Unity-aware diff that explains prefab objects, components, properties, references, nested sources, and overrides.
What should I check in a Unity prefab code review?
Check object hierarchy, components, nested prefab sources, overrides, GUID and fileID references, matching meta files, missing scripts, and whether the prefab opens in the project Unity version.
Why are prefab overrides hard to review in raw YAML?
The YAML stores property paths, target fileIDs, source links, and modification records. The reviewer must reconstruct which object and source prefab each line affects.
Can MergeSight review prefabs between UVCS changesets?
Yes. MergeSight can use concrete UVCS changesets as review sources and present supported prefab changes through semantic object, component, property, reference, and override context.
Summary
Include related assets
Review source prefabs, nested dependencies, materials, scripts, and meta files together.
Inspect prefab meaning
Focus on ownership, overrides, hierarchy, nested sources, and resolved references.
Validate in Prefab Mode
A changeset is ready only when the prefab imports, opens, and behaves as intended.
Prefab review should make source relationships and overrides understandable before a changeset reaches the merge stage.
Next step
For a deeper explanation of override records, read Unity Prefab Overrides Explained.