Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From debug-session
Guides through a structured debugging workflow — gather error info, reproduce, narrow root cause, apply minimal fix, verify, 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>
npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin debug-session2plugins reuse this command
First indexed Mar 30, 2026
/debugExecutes systematic debugging workflow end-to-end: triage issue from description, diagnose root cause, plan fix, and execute using persistent state and tools like Read, Bash, Edit.
/debugDebugs described code issues systematically: reproduces the problem, investigates root cause, applies targeted fixes, and verifies resolution.
/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.
/debugGuides methodical problem investigation with a 6-step debugging process: reproduce, isolate, analyze, hypothesize, test, and fix. Produces root cause analysis, fix recommendations, and prevention strategies.
/debugDelegates bug descriptions to Cursor's Debug mode for hypothesis-driven investigation: generates hypotheses, adds logs, pinpoints issues, and applies targeted fixes.
/debugPerforms 4-phase systematic debugging on a bug: reproduce, root cause analysis with tests, TDD fix, and defense-in-depth verification.