targeted-debuglisted

## Live context !`git rev-parse --show-toplevel 2>/dev/null && echo "repo: $(basename $(git rev-parse --show-toplevel))" || echo "not a git repo"` !`git branch --show-current 2>/dev/null | sed 's/^/branch: /' || true` > The `!`-prefixed lines above are Claude Code dynamic frontmatter. Harnesses that do not > expand them render them as literal text and lose nothing else — every step below either > re-derives the repo root with `git rev-parse --show-toplevel` or works from paths as > given. If `git` is unavailable, treat every path as relative to the working directory and > say so in the report rather than guessing a root. # Targeted Debug Scope-bounded debugging. Reads **only** files explicitly named in the stack trace or by the user. Forms a hypothesis from observable evidence. Does NOT explore the codebase broadly. Does NOT launch a full investigation pipeline. ## Why this skill exists When a stack trace or error message is already in hand, broad codebase exploration adds noise without improving signal. A full investigation session is for "I don't know what's happening" — this skill is for "here's the crash, tell me why." The strict scope constraint (read only what's named) is what makes it fast, token-efficient, and precise. ## Path extraction (use the bundled script) A deterministic path extractor is available at `scripts/extract-error-paths.sh`. Run it on the raw stack trace to get the exact file list — no manual parsing needed: ```bash # From the repo root — pipe