mcpbeat

Debug Live Issue

hoangsonww/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.

346 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
867
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor --skill debug-live-issue

The instruction itself

4 sections, as written by the author

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

How to use it

Copy the folder

Take hoangsonww/debug-live-issue from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.