Unity debug
ランタイムエラー・NullReference・コンソールログの調査ワークフロー。 Use for: "エラー調査", "NullReference", "デバッグ", "コンソール確認", "ログ確認"From its SKILL.md
npx -y skills add bigdra50/unity-cli --skill unity-debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 8 commands, including `u -i <instance> console get -l E,X | head -20` and 7 more.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.1 KB, 582 tokens by cl100k_base, as published. Nobody here has run it
unity-debug
PREREQUISITE:
../unity-shared/SKILL.md（Relay Server 経由で Unity Editor が起動/アクティブであること）skill 経由のコマンドは必ず
-i <instance>を付ける (unity-shared #インスタンス指定)。
調査フロー
1. エラー取得 u -i <instance> console get -l E,X | head -20
2. エラー分類 → コンパイルエラー / ランタイムエラー / Missing 系
3. コンテキスト収集 u -i <instance> scene hierarchy / u -i <instance> component inspect / u -i <instance> screenshot
4. 原因特定 → 修正 → /unity-verify で検証
エラー分類と対応
| エラー種別 | 対応 |
|---|---|
| CS0XXX (コンパイルエラー) | コード修正 → /unity-verify |
| NullReferenceException | u -i <instance> scene hierarchy + u -i <instance> component inspect で参照確認 |
| MissingReferenceException | u -i <instance> asset info でアセット存在確認 |
| MissingComponentException | u -i <instance> component list で確認 → u -i <instance> component add |
コンソール操作
u -i <instance> console get # 全ログ
u -i <instance> console get -l E | head -10 # Error のみ、先頭10件
u -i <instance> console get -l E,W # Error + Warning
u -i <instance> console clear # ログクリア
状態確認
u -i <instance> screenshot # エディタのスクリーンショット
u -i <instance> scene hierarchy # 現在のシーン構造
u -i <instance> state # Play/Pause/Compile 状態
コンパイルエラーが解決しない場合は /unity-verify に切り替える。
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most debug triage skills give in 582 tokens
Counted across 1,020 of the 1,639 authors here whose files we hold, read 2026-09-06
- Find root cause before attempting any fixin 134 of 1020, across 118 files
- Create a failing test case before implementing a fixin 109 of 1020, across 95 files
- Read error messages and stack traces completelyin 102 of 1020, across 88 files
- Reproduce the issue consistently before investigatingin 90 of 1020, across 77 files
- Make the smallest possible change to test a hypothesisin 90 of 1020, across 76 files
- Trace data flow backward to find the sourcein 84 of 1020, across 70 files
- Form a single hypothesis before testingin 78 of 1020, across 64 files
- Implement only one fix at a timein 76 of 1020, across 63 files
- Question the architecture if three fixes failin 73 of 1020, across 59 files
- Add diagnostic instrumentation at component boundariesin 68 of 1020, across 56 files
- Compare broken code against working examplesin 68 of 1020, across 57 files
- Write a regression test before applying the fixin 62 of 1020, across 55 files
Said here and by no other author read
- Include instance flag in all commands
- Fetch console logs to identify error type
- Inspect scene hierarchy for context
- Inspect components for null references
- Verify asset existence for missing references
- List components to resolve missing component errors
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.