メニュー
Structured bug investigation workflow for UnravelEngine: reproduce, isolate domain, find root cause, minimal fix, and verify. Use for bug reports, crashes, regressions, or unexpected behavior in engine or editor.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Manages UnravelEngine asset pipeline: importers, .meta sidecars, UID stability, asset compilation, async loading, and reimport. Use for asset types, import errors, content browser issues, or compiled .asset output.
Builds and verifies UnravelEngine: CMake targets, engine_data/editor_data copy, .NET SDK / CoreCLR scripting dependency, sanitizers, and CI workflows. Use after code changes, before marking work complete, or when fixing build/CI failures.
Creates and edits UnravelEngine scene entities via Editor MCP: hierarchy, coordinate system (X-right Y-up Z-forward), WORLD vs LOCAL transforms, components, ScriptComponent source, and scene_save. Use when spawning primitives, parenting, placing children, attaching C# scripts, or persisting .spfb scenes.
Creates and edits UnravelEngine PBR materials via Editor MCP tools or code. Use when changing .mat assets, model material slots, runtime material instances, or deciding asset vs instance edit paths.
Opens/closes UnravelEngine editor projects, lists recent projects, and opens or creates scenes from defaults::scene_preset via Editor MCP. Use when switching projects, loading .spfb scenes, or bootstrapping a new preset scene.
Works on UnravelEngine managed scripting: C# API, script glue, hot-reload, ScriptComponent lifecycle, and C++/C# interop via dotnetpp (CoreCLR). Use for game scripts, scripting backend, OnCreate/OnUpdate hooks, or physics/UI events forwarded to C#.
| name | unravel-bug-investigation |
| description | Structured bug investigation workflow for UnravelEngine: reproduce, isolate domain, find root cause, minimal fix, and verify. Use for bug reports, crashes, regressions, or unexpected behavior in engine or editor. |
| disable-model-invocation | true |
Run unravel-triage to classify domain. Gather:
git log, git diff)If not reproducible: ask for scene file, project settings, or video — but keep investigating logs/code paths meanwhile.
Narrow the failure surface:
| Symptom | First reads |
|---|---|
| Render/visual | unravel-rendering, viewport, pipeline |
| UI/layout | unravel-editor-panel, ImGui ID conflicts |
| Crash on play | on_play_begin handlers, physics, scripts |
| Save/load | serialization, meta, prefab paths |
| Asset missing | unravel-assets, UID, .meta |
| Script error | unravel-scripting, managed / editor console |
| Performance | unravel-profiler-debug |
Use logging (APPLOG_*), breakpoints, or stats overlay as appropriate.
Do not apply speculative fixes without evidence.
deps/3rdparty edits unless unavoidableunravel-build-verify)If user corrected approach: run unravel-lessons to record pattern.
When presenting fix to user:
## Root cause
[One sentence]
## Fix
[What changed and why]
## Verification
[What was tested]