Stats
Actions
Tags
From pbr
Performs systematic debugging of the codebase using hypothesis testing. Maintains persistent state across sessions for ongoing analysis.
How this command is triggered — by the user, by Claude, or both
Slash command
/pbr:debugThe summary Claude sees in its command listing — used to decide when to auto-load this command
This command is provided by the `pbr:debug` skill.
This command is provided by the pbr:debug skill.
npx claudepluginhub sienklogic/plan-build-run/debugInvokes oac:debugger skill to diagnose bugs, test failures, or unexpected behavior exactly as specified, before any fix proposals.
/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.
/fire-debugDebugs issues systematically with scientific method, subagent isolation, persistent sessions, skills library integration, and live docs lookup.
/investigateInvestigates bugs via structured root cause analysis: scopes to module, collects evidence, forms hypotheses, implements evidence-based fixes.
/debugRuns the scientific debugging method (STABILIZE→LOCATE→HYPOTHESIZE→EXPERIMENT→FIX→TEST→SEARCH) on an active bug or failing test. Also supports auditing whether a prior debugging session was systematic.