debug-live-issue
The debug-live-issue skill provides a structured workflow for diagnosing production-like failures across hooks, API routes, databases, websockets, and UI components. Use it when troubleshooting failing workflows, regressions, flaky tests, or data inconsistencies by systematically capturing symptoms, isolating affected subsystems, reproducing issues with minimal scope, and gathering evidence before applying fixes.
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor /tmp/debug-live-issue && cp -r /tmp/debug-live-issue/.claude/skills/debug-live-issue ~/.claude/skills/debug-live-issueSKILL.md
# 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`
Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
Review React UI changes for behavior regressions, state consistency, and UX breakage.
Review MCP server changes for tool safety, schema quality, and host integration correctness.
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.
Implement a feature safely end-to-end in this repository. Use when adding or changing functionality across backend, frontend, or MCP with required verification and documentation updates.