debug-fixed
User confirms the bug is fixed. Clean up instrumentation and summarize.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
User confirms the bug is fixed. Clean up instrumentation and summarize.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Hypothesis-driven debugging with runtime log instrumentation. Use when user reports a bug, unexpected behavior, flaky test, or when runtime evidence is needed to understand code behavior. Invoke for issues like "X isn't working", "I'm seeing Y error", "why does Z happen", or when multiple code paths could cause the problem.
User confirms the bug was reproduced. Analyze logs and iterate on hypotheses.
| name | debug-fixed |
| description | User confirms the bug is fixed. Clean up instrumentation and summarize. |
User confirms the bug is fixed. Clean up and summarize.
$ARGUMENTS
Remove all __debugLog() calls from instrumented files:
__debugLog(...) callsappendFileSync, mkdirSync, existsSync)bun ./scripts/stop-collector.mjs
Provide a brief summary:
Root Cause: [Which hypothesis was confirmed and why]
Fix Applied: [What change fixed the issue]
Files Modified: [List of files that were changed]
Root Cause: Hypothesis A confirmed -
itemsarray wasundefinedwhenorder.itemswasn't provided by the caller, causing "Cannot read property 'length' of undefined"Fix Applied: Added null check with default empty array:
const items = order.items ?? []Files Modified:
src/api/orders.ts- Added defensive check inprocessOrder()
The .debug/ directory can be left in place (it's gitignored) or removed:
rm -rf .debug