error-detective

Analyzes logs and stack traces to identify error patterns and root causes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging production issues often means digging through massive log files and scattered stack traces across multiple services. This Skill structures that investigation by extracting error patterns, correlating failures across systems, and forming evidence-based root cause hypotheses. ## Core Features & Use Cases - Log Parsing & Error Extraction: Generates regex patterns to pull errors, stack traces, and anomalies from raw log streams. - Cross-System Correlation: Links errors across distributed services, deployments, and time windows to detect cascading failures. - Root Cause Analysis: Works backward from symptoms to identify likely code locations and produces monitoring queries to detect recurrence. - Use Case: After a production deploy triggers a spike in 500 errors, use this Skill to parse aggregated logs, correlate the spike with the deployment timeline, and pinpoint the failing service and code path. ## Quick Start Analyze the attached application logs to find error patterns, correlate failures across services, and propose a root cause with monitoring queries.

Frequently Asked Questions about error-detective

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

FAQPage Schema
How do I find root causes from application logs?▼

Start with the error symptoms and work backward to the cause. Extract error patterns with regex, build a timeline of occurrences, correlate them with deployments or changes, and check for cascading failures across services.

How to correlate errors across distributed systems?▼

Correlate errors by aligning timestamps across service logs, tracing request flows between components, and checking whether one service's failure triggers downstream errors. Look for error rate spikes that coincide across systems.

What regex patterns extract errors from log files?▼

Effective patterns target log levels like ERROR or FATAL, exception class names, and stack trace headers. The Skill generates extraction regexes tailored to your log format, covering common patterns and anti-patterns across languages.

Does this work with Elasticsearch or Splunk logs?▼

Yes, the Skill covers log aggregation queries for Elasticsearch and Splunk. It produces monitoring queries you can run in these platforms to detect error recurrence and track anomaly trends in log streams.

When is log analysis not enough to find root cause?▼

Log analysis falls short when logging is incomplete, errors are swallowed silently, or the failure stems from infrastructure outside logged systems. In those cases, combine log findings with metrics, tracing, or direct code inspection.