debug-live-issue

Featured

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.

Web & Frontend 989 stars 233 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
33
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
hoangsonww
Repository
hoangsonww/Claude-Code-Agent-Monitor
Created
6 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Integrates with

SQLite · Database Tailwind CSS · Frontend Express.js · Backend WebSocket · API

Bundled in these plugins

Claude-Code-Agent-Monitor

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

debug

Diagnose a non-trivial bug through reproduction, evidence gathering, hypothesis testing, root-cause analysis, a minimal fix, and regression verification. Use when the cause is not already obvious.

1 Updated 1 weeks ago
martonpaulo
Code & Development Listed

debugging-production-systems

Use when debugging a bug in a deployed/self-hosted production system — especially errors surfaced inside third-party widgets or iframes, "works locally but fails in prod", suspected stale deploys or browser caches, regressions after a deploy, or when the fix requires SSH to a server, querying production data, reading CI/deploy logs, or reproducing browser-only failures. Use before proposing fixes when a debugging session risks becoming a multi-deploy spiral.

1 Updated today
MwiniSaviour
Code & Development Featured

debug

Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix for code changes.

775 Updated today
kdlbs