From debug-session
Guides an interactive debugging session: gather error info, reproduce, narrow cause, fix root issue, and add a regression test.
How this command is triggered — by the user, by Claude, or both
Slash command
/debug-session:debugThe summary Claude sees in its command listing — used to decide when to auto-load this command
Start an interactive debugging session to diagnose and fix a runtime issue. ## Steps 1. Gather the error information: 2. Reproduce the issue: 3. Narrow down the failure point: 4. Examine the root cause: 5. Implement the fix with minimal changes. 6. Verify the fix resolves the issue. 7. Add a test that reproduces the original bug. 8. Remove any temporary logging added during debugging. ## Format ## Rules - Always reproduce before attempting to fix. - Remove all debug logging before committing. - Fix the root cause, not just the symptom.
Start an interactive debugging session to diagnose and fix a runtime issue.
Issue: <description>
Reproduction: <steps>
Root Cause: <what went wrong>
Fix Applied: <changes made>
5plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub smarks26/awesome-claude-code-toolkit --plugin debug-session/debugGuides an interactive debugging session: gather error info, reproduce, narrow cause, fix root issue, and add a regression test.
/debugWalks through a structured debugging workflow: gathers bug reports, traces execution paths, forms and tests hypotheses, then implements fixes with regression tests.
/debugExecutes a systematic debugging workflow with persistent state: triage, diagnose root cause, plan fix, and execute. Preserves workflow gates, validations, and checkpoints.
/debugDebugs described code issues systematically: reproduces the problem, investigates root cause, applies targeted fixes, and verifies resolution.
/debugGuides systematic debugging: intake symptom, form hypotheses, gather evidence, find root cause, propose fix, and document results.
/debugSpawns a deep-thinking agent to systematically debug errors, bugs, stack traces, or unexpected behavior from arguments or context, producing analysis, hypotheses, and code fixes.