Stats
Actions
Tags
From spk
Systematic root-cause debugging. Diagnose first, no fixes until evidence proves the cause.
How this skill is triggered — by the user, by Claude, or both
Slash command
/spk:debug [bug, failing test, error output, or reproduction steps][bug, failing test, error output, or reproduction steps]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run a systematic root-cause investigation before any fix is attempted.
Run a systematic root-cause investigation before any fix is attempted.
Use this for failing tests, production bugs, build errors, regressions, unexpected behavior, or any situation where guessing would waste time.
!git status --short
!git log -5 --oneline
!git diff --stat
Dispatch: Task(subagent_type="spk:debugger", prompt="Systematically debug this issue: $ARGUMENTS. Follow the 4-phase RCA process: (1) read errors and reproduce, (2) compare working patterns, (3) form and test one hypothesis at a time, (4) recommend the smallest fix and regression test. Do not modify source code. Return evidence, root cause, affected file:line locations, and recommended next action.")
Expect: a diagnosis, not a patch.
NEEDS_REPRO with exact missing information.POSSIBLE_ARCHITECTURE_ISSUE instead of proposing a fourth patch.npx claudepluginhub apipoj/spk --plugin spkGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.