Claude Code /debug Skill

Resource overview Purpose
• Bundled Claude Code debugging skill for investigating failing behavior, logs, stack traces, tests, and runtime issues.

Recommended SKILL.md contents
• Trigger description explaining when Claude should use the skill.
• Step-by-step procedure for the workflow.
• Required checks before edits or publication.
• Verification command or manual acceptance checklist.
• Links to supporting examples, scripts, or templates when the workflow needs them.

What it helps you do

Use this skill because it keeps debugging systematic instead of jumping directly to speculative edits.

Skills load their full instructions only when used, which keeps normal session context smaller.

A reusable `SKILL.md` gives teams a versioned workflow instead of repeated ad hoc prompts.

Best fit users

backend, frontend, mobile, AI, and platform engineers debugging production-like issues.

Teams standardizing AI-assisted delivery across multiple repositories.

Builders who want Claude to apply consistent procedures without repasting instructions.

What to know first

a reproducible error, stack trace, failing test, log output, or exact observed behavior.

A skill directory such as `.claude/skills/<skill-name>/SKILL.md` or `~/.claude/skills/<skill-name>/SKILL.md`.

A concise frontmatter description so Claude can decide when to load the skill.

Environment needed

project checkout, runtime dependencies, test command access, and safe permission to run diagnostic commands.

Claude Code skill support and access to the files or commands the workflow needs.

Any external APIs, MCP servers, credentials, or local runtimes required by the specific workflow.