debug-live-issue
SolidDebug 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 456 stars
91 forks Updated yesterday MIT
Install
Quality Score: 89/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
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
- 3 months ago
- Last Updated
- yesterday
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
Code & Development Listed
debugger
Troubleshoot production issues by reproducing, isolating root cause, applying minimal fixes, and verifying outcomes.
6 Updated yesterday
sharmasuraj0123 Code & Development Listed
debugging
Use to debug failures, reproduce symptoms, isolate causes, inspect evidence, and fix bugs.
1 Updated 6 days ago
kreek AI & Automation Solid
debugging
Systematic debugging of issues — use when a test fails, runtime error occurs, unexpected behavior is reported, or an awareness tick produces anomalous results
77 Updated today
WingedGuardian