Diagnose production errors by correlating logs, traces, and code paths.
npx skills add https://github.com/dhnt/dhnt --skill diagnose-error
Please help me install this Agent Skill. Skill: diagnose-error Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/operate/diagnose-error Command: npx skills add https://github.com/dhnt/dhnt --skill diagnose-error
Diagnose an incident by turning limited production evidence (logs, traces, metrics, and user reports) into a confirmed root cause and actionable next steps.
Use diagnose-error when an on-call alert reports a production error and you need to work from the first log occurrence to the exact failing code location and a confirmed root cause.
High-intent search queries and answers about installing and using this skill.
To find the root cause of a production error, reconstruct the symptom, trace the failing request by correlating request IDs and timestamps, and inspect the exact code path that violates an invariant to isolate causal factors.
Correlate recent deploys with an incident response alert by capturing the exact symptom, matching error timing against deployment history, and validating the suspected mechanism through hypothesis testing or reproduction steps.
Trace a failing request with incomplete distributed tracing by locating the originating log line, reconstructing the request trace via request ID and timestamp correlation, and reading the code at the failing line to identify the violated invariant.
Yes, you can reproduce a production bug during an on-call workflow by capturing precise symptom details, identifying the failing code path, and validating the hypothesis through targeted tests or reproduction steps despite incomplete telemetry.
Incident response requires documenting the root cause and reproduction steps to produce a clear writeup that preserves the exact error context, validates the causal mechanism, and provides actionable recommendations for resolution.
Diagnosing errors with limited production evidence requires precise symptom capture and log correlation to prevent losing the thread, because incomplete traces force you to rely on reading the exact failing code path and validating hypotheses via tests.
rbah31Investigate production symptoms and generate structured incident reports from logs, metrics, and traces.
unblockedGenerate ranked remediation options for incidents from parsed context and historical fixes.
ajianazOrchestrate end-to-end observability and monitoring for complex applications.
wfukatsuDesign observability systems with SLI/SLOs, distributed tracing, and log aggregation.
