unity-reviewer

Automated Unity code review detects performance anti-patterns, lifecycle order issues, and unsafe main-thread usage in C# scripts, delivering severity-ranked findings with actionable fixes.

Common Unity performance problems include calling GetComponent or GameObject.Find inside Update loops, hot path allocations, and mis-timed Update versus FixedUpdate usage, which automated review can flag.

Unity null handling affects correctness because destroyed GameObjects behave differently from standard C# null, requiring specialized checks during code review to prevent runtime crashes and unexpected behavior.

You can enforce serialized fields over public variable exposure during Unity code reviews to improve maintainability, preventing unsafe public access while still allowing Unity Inspector configuration.

Check for event unsubscription in Unity MonoBehaviour scripts during post-implementation code review to prevent memory leaks and ensure proper object lifecycle cleanup when behaviors are disabled or destroyed.

Automated Unity code review catches unsafe main-thread usage violations, detecting calls that can cause runtime errors or crashes when Unity APIs are accessed incorrectly outside expected execution contexts.