Stats
Actions
Tags
From dream-team
Debugs described code issues systematically: reproduces the problem, investigates root cause, applies targeted fixes, and verifies resolution.
How this command is triggered — by the user, by Claude, or both
Slash command
/dream-team:debugThe summary Claude sees in its command listing — used to decide when to auto-load this command
If no arguments were provided, stop immediately and tell the user: "Usage: /dream-team:debug <describe what's broken>". Do not proceed.
Read `${CLAUDE_PLUGIN_ROOT}/skills/debug/SKILL.md` and follow its instructions exactly.If no arguments were provided, stop immediately and tell the user: "Usage: /dream-team:debug <describe what's broken>". Do not proceed.
Read ${CLAUDE_PLUGIN_ROOT}/skills/debug/SKILL.md and follow its instructions exactly.
npx claudepluginhub ratler/dream-team --plugin dream-team/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.
/debugInvokes debug-like-expert skill to systematically debug the specified issue via evidence gathering, hypothesis testing, and verification.
/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.
/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.
/debugStarts systematic debugging workflow for provided bug description using Read, Edit, Write, Bash, Glob, Grep, Task, Skill tools to diagnose and fix issues.
/debugInvokes oac:debugger skill to diagnose bugs, test failures, or unexpected behavior exactly as specified, before any fix proposals.