debug-live-issue — Claude Code skill: what it does, how to install
debug-live-issue walks an agent through incident-style debugging: pin down the symptom, isolate the subsystem, reproduce, prove the cause, then apply a minimal fix.
MIT ★ 1,198 updated 2026-10-23
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill debug-live-issue -a claude-codeWhat debug-live-issue does
The skill turns debugging into a fixed sequence. First it records the symptom, the expected behavior, and a reproducible path. Then it isolates the subsystem at fault — hook ingestion, an API route, database state, websocket, or UI rendering — before touching any code.
A reference file, references/investigation-template.md, backs the workflow during an investigation. The evidence bar is strict: logs, actual API responses, database state checks, and deterministic repro steps take priority over guesses. When a bug can't be fully reproduced, the agent has to say so and name its strongest hypothesis instead of pretending to certainty.
Nothing here is tied to a particular stack or language; it's a process for reasoning through a failure, not a set of debugging commands.
What it helps with
- work through a failing workflow step by step instead of guessing
- pin down which subsystem is actually broken
- prove a root cause before touching code
- write down a reproducible path for a regression
- separate a confirmed cause from a hunch
Example prompts for the agent
- Debug this failing workflow using debug-live-issue
- Apply debug-live-issue to the data mismatch between the API and the websocket
- Isolate the subsystem and find the root cause of this flaky test with debug-live-issue
How to install debug-live-issue
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill debug-live-issue -a claude-code2Manually: put the files in place
~/.claude/skills/debug-live-issue/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/debug-live-issue/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill debug-live-issue -a codex2Manually: put the files in place
.agents/skills/debug-live-issue/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill debug-live-issue -a cursor2Manually: put the files in place
.cursor/skills/debug-live-issue/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hoangsonww/Claude-Code-Agent-Monitor .claude/skills/debug-live-issue2Manually: put the files in place
.github/skills/debug-live-issue/SKILL.md1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill debug-live-issue -a gemini-cli2Platform CLI
gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor --path .claude/skills/debug-live-issueManually: put the files in place
.devin/skills/debug-live-issue/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about debug-live-issue
How do I install debug-live-issue in Claude Code?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill debug-live-issue -a claude-code; the skill then lives at ~/.claude/skills/debug-live-issue/SKILL.md.
What does debug-live-issue do?
It enforces a disciplined incident workflow: capture the symptom, isolate the subsystem (hooks, API, database, websocket, UI), reproduce with minimal surface area, prove the root cause, and only then apply a minimal fix.
What evidence does debug-live-issue require before a fix?
Direct logs, real API responses, database state checks, and deterministic repro steps; if the issue isn't fully reproducible, the agent must state its uncertainty and strongest hypothesis rather than guess.
Source text
SKILL.md · MIT
--- name: debug-live-issue description: Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI. --- # Debug Live Issue Use this workflow for incident-style debugging. ## Steps - Capture symptom, expected behavior, and reproducible path. - Isolate subsystem first: hook ingestion, API route, DB state, websocket, or UI rendering. - Reproduce with minimal surface area. - Prove root cause before changing code. - Apply minimal fix and re-verify. ## Evidence standards - Prefer direct logs, API responses, DB state checks, and deterministic repro steps. - Avoid speculative fixes without root-cause evidence. - If not fully reproducible, state uncertainty and strongest hypothesis. ## References - Investigation template: `references/investigation-template.md`
© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor