shadow-debug

What it does and when to use it

Diagnose and fix a reported failure using a reproducible symptom, a focused cause investigation, and regression verification. Use for broken behavior, errors, crashes, or failing checks.

How it works

SKILL.md has no level-two headings · 13 lines, 193 words

---
name: shadow-debug
description: Diagnose and fix a reported failure using a reproducible symptom, a focused cause investigation, and regression verification. Use for broken behavior, errors, crashes, or failing checks.
---

# Diagnose and repair

Honor diagnosis-only or analysis-only requests: report the evidence and likely correction without editing files. Continue into repair only when fixing the problem is within the requested scope.

Establish the exact symptom, expected behavior, and smallest reproduction available from the request and project. Preserve data and rollback options proportional to the impact. Inspect relevant logs and source without exposing private values.

Test a cause hypothesis against evidence before changing multiple layers. Distinguish the failing component from downstream symptoms. If a reproduction is unavailable, make the uncertainty explicit and use a bounded fixture that exercises the suspected path.

Fix the cause with a coherent change, then rerun the original reproduction or the closest valid equivalent. Add a meaningful regression test when the failure could recur. Check adjacent behavior affected by the fix, then stop when the acceptance conditions hold.

After repeated failures, use the new evidence to revise the hypothesis; do not repeat the same attempt indefinitely or silently reset user state. Report the remaining blocker if the original environment cannot be exercised. A mock, running process, successful build, or isolated fixture is not proof that the user's original scenario works.

Versions

The database has no other skills named shadow-debug.

Database snapshot: 13.11.2026 · package version f2dd369ea6e9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100debug
  Diagnose a failing test, build, crash, regression, or unexpected behavior without editing source. Reproduce the symptom, test hypotheses, identify the supported root cause, and hand off a repair. Use for /debug, root-cause investigation, or questions about why something is broken.
• 100debug
  Diagnose a failing test, build, crash, regression, or unexpected behavior without editing source. Reproduce the symptom, test hypotheses, identify the supported root cause, and hand off a repair. Use for /debug, root-cause investigation, or questions about why something is broken.
• 91debug-agent
  Diagnose and fix software bugs through scoped reproduction, causal investigation, focused repairs and regression verification. Use for debugging requests, especially pause, checkpoint/resume and hook failures; skip feature development and conceptual questions without a fault to investigate.
• 100debug-failure
  Find the root cause of an error, crash, failing test, regression or wrong behaviour, then fix it with a regression test. Use this whenever something is broken or behaves unexpectedly and the cause is not already proven, even if a fix seems obvious. Do not guess at fixes.
• 100oma-debug
  Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
• 86vibe-debug
  Diagnose and fix a reproducible failure in an existing project. Use for crashes, broken behavior, or failing checks, not greenfield planning.