---
description: "Hypothesis-driven debugging with runtime evidence — Sentry, Firecrawl, and Sequential Thinking, not guessing"
argument-hint: "[error or symptom]"
---

# /debug-issue

> Hypothesis-driven debugging with runtime evidence — not guessing.

This command is a thin entry point. The full playbook lives in the **`debug-error`** skill, which integrates Sentry MCP for production context, Firecrawl for fix-pattern research, and Sequential Thinking for multi-step diagnosis.

> **Named `/debug-issue` (not `/debug`)** to avoid colliding with Claude Code's bundled `/debug` skill.

Use `/debug-issue` to explicitly enter debug mode. Otherwise, say "debug this", "investigate the bug", or "why isn't this working" and the skill auto-fires.

Related: `debug-fe-be-integration` for API/contract bugs, `debug-sentry-monitor` for production triage.