error-detective

Analyze logs and exceptions to identify root causes of failures.

22|2|Updated Mar 24, 2026

Search Tags:#debugging #logs #exceptions #analyze #root-cause #incident #stack-trace

Ready to run

npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill error-detective-jshsakura

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-detective
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/error-detective
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill error-detective-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes logs, exceptions, and stack traces to identify the most probable failure source quickly.

Core Features & Use Cases

Evidence-driven root-cause hypotheses based on log patterns and error types
Trace stitching across service boundaries using correlation IDs and timestamps
Actionable remediation guidance and risk assessment for incident responders
Supports post-mortem reviews by summarizing failure propagation and impact

Quick Start

Provide the latest log excerpt, exception message, and stack trace to triage the root cause.

Frequently Asked Questions about error-detective

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

FAQPage Schema

How do I analyze logs and stack traces to find a root cause?▼

To analyze logs and stack traces for root cause identification, provide the exception message and log excerpts. The Skill correlates events by timestamps and correlation IDs to generate evidence-based remediation steps.

Can I trace exceptions across microservices using correlation IDs?▼

Yes, you can trace exceptions across microservices using correlation IDs. The Skill stitches traces across service boundaries by matching timestamps and correlation IDs to summarize failure propagation.

What is the best way to investigate incidents in distributed systems?▼

The best way to investigate incidents in distributed systems is to analyze log patterns and error types. This Skill classifies fault types and produces concise, evidence-driven hypotheses for incident responders.

How do I generate post-mortem summaries from cloud workload failures?▼

To generate post-mortem summaries from cloud workload failures, input the relevant logs and exceptions. The Skill summarizes failure propagation and impact to support post-mortem reviews.

Does this approach provide actionable remediation guidance for production incidents?▼

Yes, this approach provides actionable remediation guidance for production incidents. It analyzes stack traces and log patterns to assess risk and deliver concise, evidence-based steps for incident response.

Why do I need to correlate timestamps when debugging microservice exceptions?▼

You need to correlate timestamps when debugging microservice exceptions to accurately stitch traces across service boundaries. Timestamp alignment ensures precise failure propagation mapping and root-cause isolation.