Help us improve
Share bugs, ideas, or general feedback.
From debug-session
Starts interactive debugging session for runtime issues: reproduces bug, identifies root cause, applies minimal fix, verifies, adds test, and outputs structured summary.
npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin debug-sessionHow 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.
/debugSystematically debugs issues: gathers symptoms, traces execution path with git log, tests hypotheses, implements fixes, adds regression tests. Outputs Bug, Root Cause, Fix, Files, Test.
/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.
/debugGuides systematic debugging: intakes symptoms, defines problem, forms testable hypotheses, gathers evidence, identifies root cause, suggests fixes, and documents.
/hatch3r-debugInstruments code with debug logging, collects runtime logs from the user, performs root cause analysis, applies the fix, and removes all debug artifacts.
/debugRuns a 4-phase systematic debugging investigation (root cause, pattern, impact, solution) and writes an artifact to .orchestrator/debug/ before any fix is proposed.
/debugDiagnoses deployment issues for Claude Office add-in, including stale config, connection failures, and missing add-in. Guides through triage, error paste analysis, and cache clearing.
Share bugs, ideas, or general feedback.
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>