القائمة
Apply systematic root-cause investigation to the current failing task.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a GitHub Pull Request has unresolved review threads, pending reviews, stale/outdated threads, local findings ingestion, or needs mandatory final-gate proof in one PR-scoped session.
Optional after-specify refinement gate. Bridges an installed obra/superpowers brainstorming skill into the active Spec Kit spec.md without creating a second design document or replacing speckit.specify.
Diagnose the five Superpowers disciplines used by Superb and report the focused hook and standalone-command contract.
Read-only implementation critique against active Spec Kit artifacts.
Complete branch handoff after Spec Kit convergence and fresh checks.
Mandatory read-only pre-implementation gate. Reports test-first readiness while leaving task execution decisions with Spec Kit.
| name | speckit-superb-debug |
| description | Apply systematic root-cause investigation to the current failing task. |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"superb:commands/debug.md"} |
$ARGUMENTS
Resolve systematic-debugging, then bind investigation to the current failing
task or the explicit user scope. Capture the exact failure, reproduce it, trace
the data flow, compare a working example, and test one root-cause hypothesis at
a time.
When implementation was requested, add a focused failing test before the minimum fix and run focused verification. Do not broaden scope, create lifecycle state, or choose an execution topology. Return control to the owning Spec Kit implementation flow with the root cause and fresh evidence.
If the skill is unavailable, run
bash .specify/extensions/superb/scripts/bash/ensure-skills.sh --print-guidance
and direct the user to /speckit.superb.check; do not fetch skill content.