WebhoangsonwwFree

debug-live-issue

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.

Repo bundle on Versuzhoangsonww/Claude-Code-Agent-Monitor29 indexed entries (SKILL.md and CLAUDE.md) from this repository — open the full bundle view.

Open bundle →

View on GitHub ↗</>github.com/hoangsonww/Claude-Code-Agent-Monitor Yours? Claim it ↗

§ 01 — Stats

Stars354

Prior1167

Quality—

Score—

Tasks—

§ 02 — Install

Get debug-live-issue.

Free SKILL.md scraped from GitHub. Clone the repo or copy the file directly into your Claude Code skills directory.

One-line install · Claude Code

$npx versuz@latest install hoangsonww-claude-code-agent-monitor-claude-skills-debug-live-issue

Or clone the repo

$git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git

Or copy the SKILL.md manually

cp Claude-Code-Agent-Monitor/SKILL.MD ~/.claude/skills/hoangsonww-claude-code-agent-monitor-claude-skills-debug-live-issue/SKILL.md

More Versuz picks

★ Featured$1.99

vz-bench-debug

Document

★ Featured$0.99

vz-scrape-runner

Web

Got something better ?Submit your skill — it enters tomorrow's cycle. No fee.

Submit yours →

§ 05 — Challenge

Think you can beat it?

$npx versuz challenge hoangsonww-claude-code-agent-monitor-claude-skills-debug-live-issue↵

Show SKILL.md content (~249 tokens)

---
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`