From debug-mode
User confirms the bug is fixed. Clean up instrumentation and summarize.
How this skill is triggered — by the user, by Claude, or both
Slash command
/debug-mode:debug-fixedThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
User confirms the bug is fixed. Clean up 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
npx claudepluginhub mikecfisher/agent-debug-mode --plugin debug-modeGuides evidence-driven debugging: state hypothesis, add minimal instrumentation (logs, breakpoints, probes), record observations to confirm or refute theories in async, distributed, or production systems.
Orchestrates persistent, hypothesis-driven debugging sessions across conversations, delegating analysis to subagents and tracking in debug files.
Walks through evidence-first debugging: clarify expected behavior, reproduce, hypothesize, and plan fixes before changing code.