skills/unity-review-local/SKILL.md
Use this skill to review locally changed Unity C# files. Use when the user asks to "review my code", "check changes", or specific file paths without PR context.
npx skillsauth add cuozg/oh-my-skills unity-review-localInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Review locally changed Unity C# files by adding inline // ── REVIEW comments.
| User Request | Diff Command | Scope |
| ----------------------------- | --------------------- | -------------------------------- |
| "review my changes" (default) | git diff HEAD | All unstaged + staged changes |
| "review staged changes" | git diff --cached | Only staged changes |
| "review this file" + path | Read full file | Specific file(s), no diff needed |
| "review since last commit" | git diff HEAD~1 | Changes in last commit |
If no changes found: Check git status. If working tree is clean, inform user.
If scope is big: Ask the user which specific criteria they need to review.
From the diff output, group files by type (.cs, .prefab, .unity, .mat, .shader). Ignore .meta.
Review diff hunks first. Only fetch surrounding methods/assets when needed. Do not read the full file by default.
See unity-standards/references/review/parallel-review-criteria.md for the strict schema and subagent prompt.
Insert // ── REVIEW comments directly above the problem line using the finding's title, impact, evidence, and fix_direction:
// ── REVIEW {icon} {LABEL} #{category}
// What: {title}
// Why: {impact} - {evidence}
// Fix: {fix_direction}
null-safety lifecycle state concurrency allocation serialization event-leak logic security architectureApply only trivial, safe, single-line fixes:
if (component != null)Awake/Start fieldOnDisable/OnDestroyCompareTag replacement for tag ==[FormerlySerializedAs] for renamed fieldsNever apply multi-line refactors, architectural changes, or behavioral modifications. Leave those as // ── REVIEW comments.
Never commit review changes — leave for inspection.
tools
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
tools
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
tools
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
development
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.