Project Integrity Bot reviews the Unity-specific failure modes general linters miss—meta/GUID problems, serialized reference breakage, Git LFS mistakes, and dependency drift—and points to the exact files involved.
Only policy-relevant changes are raised.
A quiet PR check that comments only on definite and high-confidence findings, with the evidence and repair path beside each one.
The first pilot uses the subset that matches your workflow. The rest stay out of the way until they earn their place.
Find missing, orphaned, duplicated, or unexpectedly regenerated Unity meta identifiers.
Inspect changed YAML for references that point to removed or unavailable project objects.
Catch large binaries committed directly, missing pointers, and tracked-file rule drift.
Review manifest and lockfile changes together and call out unresolved or surprising dependency movement.
Detect high-signal changes to scenes, prefabs, and project settings that deserve explicit review.
Every finding includes a path, reason, confidence level, and suggested next check.
No platform migration and no quarter-long rollout. We start with one decision your team currently has to make without enough evidence.
Agree on one repository, target, baseline, CI job, and the signals that should be visible.
Wire a read-only analysis step into the current workflow and produce an example report.
Run it against representative changes, tune noise, and decide whether the next scope is justified.
Generic tools understand Git and file formats, but not the relationships between Unity meta files, GUIDs, serialized objects, and package state. The pilot focuses on those engine-specific edges.
The default gate is deliberately conservative: definite and high-confidence findings only. Lower-confidence rules can be reported separately after the team decides they are useful.
A first check on one repository covering an agreed rule set, posting to your current pull-request surface. We validate it against representative historical failures before treating anything as a gate.
We will tell you what a useful one-week pilot can cover—and what it cannot.
outreach@xesoft.dev ↗