메뉴
Install cdb.exe (Windows SDK Debugging Tools) for live process debugging. Use when the debugger skill reports cdb.exe is not found, or when you need cdb.exe and it's not installed. This is a one-time setup — once installed, cdb.exe persists across sessions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
GitHub release management for OpenChaos — guides user through building, packaging, and publishing releases, and generates release notes with the established format. Use this skill whenever the user asks to create/prepare a release, write release notes, generate a release description, or mentions publishing to GitHub releases. Trigger on: "релиз", "release", "release notes", "описание релиза", "напиши описание", "подготовь релиз", "сделай релиз", "write release notes", "generate release description".
AddressSanitizer (ASan) — runtime memory error detector for finding heap overflows, use-after-free, stack-use-after-scope, global buffer overflows, and other memory bugs. Use this skill whenever crash investigation suggests memory corruption: OpenChaos.crash_log.txt shows heap corruption, access violations in system DLLs (NVIDIA, ucrtbase), CRT debug asserts on heap, inconsistent/variable crash symptoms, or crashes that move around between runs. Also use when the user says "memory bug", "heap corruption", "asan", "sanitizer", "buffer overflow", "use-after-free", or when you suspect memory issues yourself during debugging. Even if the user doesn't mention ASan explicitly, if the crash pattern looks like memory corruption (random crashes, heap asserts, driver DLL crashes), proactively suggest using this skill.
Temporary runtime debug logging to file for investigating rendering bugs, game state, variable values, call traces, etc. Use this skill whenever you need to see what's happening inside the game at runtime — values that only exist during gameplay, render state during specific frames, variable changes over time. Trigger when: you need runtime data to diagnose a bug, the user reports a visual glitch or wrong behavior that requires seeing internal values, or when OpenChaos.crash_log.txt and debugger attach aren't enough because you need to observe values across many frames. Also use when you say to yourself "I wish I could see what X equals during gameplay" — that's exactly what this skill is for.
Attach to the running game process with cdb (Windows debugger) to inspect stack traces, variables, and game state. Use for crash investigation, freeze debugging, and understanding what the game is currently doing. Use this skill whenever the game is frozen/hung and crash handler didn't fire, when you need to read a global variable's current value, or when OpenChaos.crash_log.txt isn't enough and you need live process inspection. Also consider this skill when the user describes behavior that suggests the game is stuck in a loop or waiting on something. TRIGGER: user says "attach", "where am I", "what's happening", "it froze", "hang", "зависло", "подключись", "посмотри что происходит", "повисло", "не отвечает", "game stuck".
General self-review for OpenChaos — runs after ANY code changes, not just before commits. Use this skill whenever work is done: after a migration iteration, after fixes, after any edits. The user commits manually and may not commit at all — review is still mandatory every time code is touched. Also use when the user explicitly asks for review. Trigger on: "проверяй", "ревью", "готово", "самопроверка", "review", "check", "проверь", "посмотри что поменял", or automatically after completing any batch of code changes. For Stage 4 migration, also trigger stage4-review.
How to draw in-world 3D debug primitives (lines, spheres, axes, markers) in OpenChaos — what's available, the historical render-pass guard gotcha, the g_matWorld pollution gotcha, naming conventions, and how to add a new debug primitive. Use this whenever you need to visualise something in world space for diagnostics — bone positions, hit points, ray traces, AI paths, collision shapes, physics queries, sample points, anything you want to look at on top of the rendered scene. NOT for 2D screen-space text overlays — those go through the separate text-rendering / debug-log skills.
| name | debugger-install |
| description | Install cdb.exe (Windows SDK Debugging Tools) for live process debugging. Use when the debugger skill reports cdb.exe is not found, or when you need cdb.exe and it's not installed. This is a one-time setup — once installed, cdb.exe persists across sessions. |
When debugger skill can't find cdb.exe at:
/c/Program Files (x86)/Windows Kits/10/Debuggers/x64/cdb.exe
curl -L -o /tmp/winsdksetup.exe "https://go.microsoft.com/fwlink/?linkid=2272610"
powershell -c "Start-Process -FilePath '$(cygpath -w /tmp/winsdksetup.exe)' -ArgumentList '/features OptionId.WindowsDesktopDebuggers /quiet /norestart' -Wait"
ls "/c/Program Files (x86)/Windows Kits/10/Debuggers/x64/cdb.exe" && echo "SUCCESS"
winget install Microsoft.WinDbg — installs the GUI Store app, NOT the CLI cdb.exewinget install Microsoft.WindowsSDK --override "/features OptionId.WindowsDesktopDebuggers" — --override is ignoredlldb -p <PID> — crashes with error: unable to find 'python311.dll' (system has Python 3.13)After installation: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe