# Debug Issue

> Use when a bug report or failing test names a symptom and the code path producing it is not yet known — trace the call chain from symptom to entry point before proposing a fix. Trigger phrases: "why does this fail", "trace this bug", "find where this is called from", "what calls this function", "did a recent change cause this". Not a replacement for the general reproduce-isolate-fix discipline (a `systematic-debugging` skill, if present, governs that overall loop); reach for this skill specifically for the tracing step — once a symptom is located and the call chain to its entry point still needs walking before a hypothesis is formed.

- Skill: `arasz/debug-issue-3` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add arasz/debug-issue-3`
- Raw SKILL.md: https://api.skillmd.com/api/skills/arasz/debug-issue-3/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- License: MIT
- Author: Arasz (https://skillmd.com/u/arasz)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/arasz/debug-issue-3

---


> **This is the generic copy.** If this project has been scaffolded, prefer the unprefixed
> `debug-issue` skill: it is `.ai-badger/skills/debug-issue/SKILL.md`, and it has this project's
> extensions and any `project-local.md` merged in. This copy has neither.
>
> The full procedure is in `SKILL.full.md` beside this file, unchanged — read it if the project has no
> `.ai-badger/`, or run `welcome-ai-badger` to scaffold one.

