Debug Live Issue

When your production workflow breaks or your tests start flaking, this skill enforces the discipline you know you should follow but often skip under pressure. It walks you through capturing symptoms, isolating the subsystem (hook, API, DB, websocket, UI), reproducing with minimal scope, and proving root cause before you touch code. The evidence standards are the real value here: direct logs and DB checks over guesses, minimal fixes over shotgun debugging. It includes an investigation template reference, which suggests this is meant for teams that want consistent incident response. Good for anyone who's shipped a speculative fix at 2am and regretted it.

GitHub stars: 455
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add hoangsonww/claude-code-agent-monitor --skill debug-live-issue --agent claude-code

Installs into .claude/skills of the current project.

Files

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.