Unity C# Code Review
Unity C# development has unique performance constraints not covered by general code review skills.
Claude Code skill for reviewing Unity C# code against Unity's Official C# Style Guide (Unity 6 Edition), covering naming conventions, SRP, MonoBehaviour lifecycle, performance, GC allocation, and common anti-patterns.
- Review game code against official Unity style guidelines
- Catch performance issues and memory allocation problems early
- Enforce naming conventions and architecture patterns in Unity projects
Unity C# development has unique performance constraints not covered by general code review skills. A Unity-specific reviewer aligned with Unity 6 standards prevents the most common and costly performance mistakes.
Unity developers building Unity 6 games or applications who want AI code review aligned with Unity's official style guidelines and performance best practices.
https://github.com/jinda-li/code-review-unity
By jindali
How to Get It
npx code-review-unity
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Help me review game code against official Unity style guidelines
Trust Signals Reviewed
Community Pulse Active
Discussed on Hacker News, Reddit
- Watch Dogs: Legion - Review Thread — Reddit · 2771 pts
- Looking for Code Review: Unity Game (C# Architecture & Clean Code) — Reddit · 17 pts
- devlo – Automate software chores like code reviews, unit testing and more — Hacker News · 3 pts
3 mentions across 2 sources
Reviewer notes
Reviewed review. These are observations, not a security certification.
audit 2026-07-05 stale-eval refresh: Scored from trust signals (evidence-eval-v1): 36 GitHub stars; 1 contributors; last commit 110d ago; license MIT.
Things to check
- Focuses on style and common patterns; won't catch game-design-specific logic flaws or complex architecture issues. Accuracy depends on whether the skill's training reflects current Unity 6 conventions—spot-check results on your codebase before using as gatekeeping.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
audit 2026-07-05 stale-eval refresh: Scored from trust signals (evidence-eval-v1): 36 GitHub stars; 1 contributors; last commit 110d ago; license MIT.