القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill to generate and apply a clear title and structured description for a GitHub Pull Request by deep-investigating all changed files. Use it when the user opens a new PR, when a PR's title or description is missing or stale, or when the user says "update this PR", "describe this PR", or "write a summary for this PR." Applies the result directly via gh pr edit.
Use when rebasing current branch onto a target branch, especially when the working tree has uncommitted changes, the local target ref may be behind its remote, or the rebase risks conflicts that need user review.
Expand a goal-create file into a detailed, implementation-ready task breakdown. Use when a user has a goal under Docs/Goals and wants it expanded into per-Task blocks (files, interfaces, code snippets, bash commands, acceptance criteria) ready to hand to goal-execute. Triggers: "detail this goal", "expand the goal", "break the goal into tasks", "create task breakdown", "plan the goal", "write implementation steps for this goal", "make an epic-style plan from this goal". Do not use for executing the goal, writing test cases, or verifying completed work.
Generate tree-format data structure documentation for Unity JSON schemas (db_*.json tables like db_TTE, db_DBSE). Use when the user pastes/shares a table of fields with short keys (a0, b1, c2...), wants a hierarchical tree diagram of a JSON data structure, asks to "create tree format", "data structure doc", "document db_XXX.json", or "generate data struct markdown". Output is a markdown file with a tree showing parent-child nesting (Object arrays → child objects) plus per-level field reference tables.
Use for Unity engineering standards: C# code, asset managers, Addressables, analytics, LiveOps, config, server API, IAP, prefab, Canvas UI, material, shader, draw calls, batching, debugging, optimization, reviews, project investigation, tests, plans, todos, acceptance criteria, and technical docs.
Diagnose Unity bugs from compile errors to stack traces, runtime failures, and tricky logic issues; gather reproduction details, trace the code path, prove the root cause with evidence, and report options without changing code unless asked.
| name | unity-review-local |
| description | 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. |
| metadata | {"author":"kuozg","version":"1.0"} |
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.