ワンクリックでManusで任意のスキルを実行

unity-review-local

スター4

フォーク0

更新日2026年5月11日 19:36

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 ページを確認してインストールできます。

Manusで実行

ソース

cuozg

cuozg/oh-my-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Unity Local Code Review

Review locally changed Unity C# files by adding inline // ── REVIEW comments.

1. Determine Review Scope

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.

2. Group Files by Type

From the diff output, group files by type (.cs, .prefab, .unity, .mat, .shader). Ignore .meta.

3. Fast and Focused Reading

Review diff hunks first. Only fetch surrounding methods/assets when needed. Do not read the full file by default.

4. Spawn Parallel Review Subagents

See unity-standards/references/review/parallel-review-criteria.md for the strict schema and subagent prompt.

When reviewing criteria with a big scope, split the work and spawn multiple subagents.

5. Aggregate and Validate

Merge findings from all subagents into a single list.
Deduplicate by (path, line) — keep highest severity.
Sort by file path → line number.
Validate high-confidence findings:
- Dead code claims — verify nothing references the symbol.
- Missing unsubscription — verify the subscription actually exists.

6. Annotate Source Files

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}

Labels: 🔴 CRITICAL, 🟠 HIGH, 🟡 MEDIUM, 🔵 LOW, ⚪ STYLE
Categories: null-safety lifecycle state concurrency allocation serialization event-leak logic security architecture

7. Apply Safe Fixes

Apply only trivial, safe, single-line fixes:

Add null check: if (component != null)
Cache GetComponent: move to Awake/Start field
Add missing unsubscription in OnDisable/OnDestroy
Add CompareTag replacement for tag ==
Add [FormerlySerializedAs] for renamed fields

Never apply multi-line refactors, architectural changes, or behavioral modifications. Leave those as // ── REVIEW comments. Never commit review changes — leave for inspection.

このリポジトリの他の Skills

同じリポジトリ

git-pr

cuozg/oh-my-skills

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.

2026-07-114

git-rebase

cuozg/oh-my-skills

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.

2026-07-114

goal-detail

cuozg/oh-my-skills

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.

2026-07-094

unity-data-struct

cuozg/oh-my-skills

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.

2026-07-084

unity-standards

cuozg/oh-my-skills

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.

2026-07-084

unity-debug

cuozg/oh-my-skills

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.

2026-06-244

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"}

Unity Local Code Review

Review locally changed Unity C# files by adding inline // ── REVIEW comments.

1. Determine Review Scope

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.

2. Group Files by Type

From the diff output, group files by type (.cs, .prefab, .unity, .mat, .shader). Ignore .meta.

3. Fast and Focused Reading

Review diff hunks first. Only fetch surrounding methods/assets when needed. Do not read the full file by default.

4. Spawn Parallel Review Subagents

See unity-standards/references/review/parallel-review-criteria.md for the strict schema and subagent prompt.

When reviewing criteria with a big scope, split the work and spawn multiple subagents.

5. Aggregate and Validate

Merge findings from all subagents into a single list.
Deduplicate by (path, line) — keep highest severity.
Sort by file path → line number.
Validate high-confidence findings:
- Dead code claims — verify nothing references the symbol.
- Missing unsubscription — verify the subscription actually exists.

6. Annotate Source Files

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}

Labels: 🔴 CRITICAL, 🟠 HIGH, 🟡 MEDIUM, 🔵 LOW, ⚪ STYLE
Categories: null-safety lifecycle state concurrency allocation serialization event-leak logic security architecture

7. Apply Safe Fixes

Apply only trivial, safe, single-line fixes:

Add null check: if (component != null)
Cache GetComponent: move to Awake/Start field
Add missing unsubscription in OnDisable/OnDestroy
Add CompareTag replacement for tag ==
Add [FormerlySerializedAs] for renamed fields

Never apply multi-line refactors, architectural changes, or behavioral modifications. Leave those as // ── REVIEW comments. Never commit review changes — leave for inspection.