SkillCurated by metahubEval warnings

debug-live-issue

Name: debug-live-issue
Author: hoangsonww

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.

pinned to #8f87ce1updated 2 weeks ago

7/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedStructuredClean repo

Ask your AI client: “install skills/debug-live-issue”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install skills/debug-live-issue

metahub onboarded this repo on the author's behalf.

If you own github.com/hoangsonww/Claude-Code-Agent-Monitor on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.

Claim this repo

Stars

789

Last commit

2 weeks ago

8f87ce1

Latest release

published

2 weeks ago

#ai-agents
#claude-agents
#claude-code
#claude-skills
#express
#expressjs
#macos-app
#node
#nodejs
#python
#react
#rest-api
#rfc-6455
#sqlite
#sqlite3
#tailwind
#tailwindcss
#typescript
#vite
#websocket

About this skill

Pulled from SKILL.md at publish time.

Use this workflow for incident-style debugging.

Evaluation report

Warnings

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.8f87ce1· 2 weeks ago

Kind-specific

Skill: SKILL.md present
found at .claude/skills/debug-live-issue/SKILL.md · frontmatter source: SKILL.md
Skill: body content presentwarn
Body is short (92 words · 661 chars) — Claude has little to go on
Add concrete usage steps, example invocations, and any reference links. (≥3 code blocks lifts a short body to pass.)
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)

Release history

releasecurrent8f87ce1warn2 weeks ago

View on GitHub

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.