Claude Skill

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.

LLM Mart · 0 points · 6 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download hoangsonww-claude-code-agent-monitor-.claude_skills_debug-live-issue-83d4df5.zip · 1 KB

hoangsonww/claude-code-agent-monitor 1014 238 forks MIT Updated 22h ago

Part of hoangsonww/claude-code-agent-monitor — 86 skills

Install

skills CLI npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/.claude/skills/debug-live-issue

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install hoangsonww-claude-code-agent-monitor@llmmart

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

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole hoangsonww/claude-code-agent-monitor collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Files (claude-code-agent-monitor)

references

investigation-template.md 465 B

# Investigation Template

## Problem statement
- Symptom:
- Expected behavior:
- First observed:
- Scope:

## Reproduction
- Preconditions:
- Exact steps:
- Actual result:

## Evidence
- Logs:
- API responses:
- Database observations:
- Websocket behavior:
- UI behavior:

## Root cause
- Confirmed cause:
- Why it happens:

## Fix
- Change summary:
- Why this fix is minimal and safe:

## Verification
- Commands/tests run:
- Manual verification:
- Residual risk:

SKILL.md 922 B

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