error-debugging-error-analysis

Diagnose production errors using stack traces, structured logs, and distributed tracing.

2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/monang404/lunawave --skill error-debugging-error-analysis-monang404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-debugging-error-analysis
Source: https://github.com/monang404/lunawave/tree/main/.agent/skills/error-debugging-error-analysis
Command: npx skills add https://github.com/monang404/lunawave --skill error-debugging-error-analysis-monang404

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Debugging production incidents and recurring errors across distributed systems is slow and error-prone without a systematic process. This Skill provides a structured methodology for root-cause analysis, log correlation, and error prevention so teams can resolve incidents faster and reduce recurrence. ## Core Features & Use Cases - Systematic Root-Cause Analysis: Classify errors by severity and type, apply the Five Whys technique, and trace failures across microservices using correlation IDs and distributed tracing. - Observability Implementation: Set up structured JSON logging, Sentry, DataDog APM, and OpenTelemetry instrumentation with alert configurations for error rate spikes and new error types. - Error Prevention Patterns: Implement circuit breakers, retry logic with exponential backoff, input validation, and React error boundaries to harden applications against failures. - Use Case: When a payment service starts throwing intermittent timeout errors in production, use this Skill to correlate logs by request ID, analyze the stack trace, identify the failing downstream dependency, and deploy a circuit breaker fix. ## Quick Start Analyze the attached production error logs and stack trace to identify the root cause and recommend a fix with preventive measures.

Frequently Asked Questions about error-debugging-error-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform root-cause analysis on production errors?▼

Root-cause analysis starts by reproducing the error, isolating the failure point, and tracing the call chain backwards. Techniques like the Five Whys, stack trace analysis, and correlation ID tracking across services help identify the true origin rather than surface symptoms.

How to track errors across microservices with correlation IDs?▼

Correlation IDs are generated at the entry point of each request and propagated through headers to all downstream services. Including the ID in every structured log entry lets you query the full request path in log aggregators like Elasticsearch or DataDog.

What is the difference between Sentry and DataDog APM for error tracking?▼

Sentry focuses on capturing exceptions with full stack traces, breadcrumbs, and release tracking, while DataDog APM provides distributed tracing, latency metrics, and service-level performance monitoring. Many teams use both together for complete observability.

When should I use a circuit breaker pattern?▼

Use a circuit breaker when calling external services that may fail or respond slowly, to prevent cascading failures. It opens after a failure threshold, rejects requests temporarily, and tests recovery in a half-open state before resuming normal traffic.

Why do intermittent errors happen only under high load?▼

Load-dependent errors typically stem from race conditions, connection pool exhaustion, or resource limits that only manifest under pressure. Diagnose them with load testing, heap snapshots, and profiling rather than standard reproduction steps.