error-detective

Analyze error patterns and stack traces to identify root causes.

Updated Feb 18, 2026

Search Tags:#error detection #root cause analysis #stack trace #log analysis #anomaly detection

Ready to run

npx skills add https://github.com/ClaudioCeppi83/kora-os-kernel --skill error-detective-claudioceppi83

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-detective
Source: https://github.com/ClaudioCeppi83/kora-os-kernel/tree/main/.agent/skills/error-detective
Command: npx skills add https://github.com/ClaudioCeppi83/kora-os-kernel --skill error-detective-claudioceppi83

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose issues by searching logs and codebases for error patterns, stack traces, and anomalies, and correlates errors across systems to identify root causes.

Core Features & Use Cases

Log Analysis: Search logs for specific error patterns and anomalies.
Stack Trace Analysis: Analyze stack traces across different programming languages.
Error Correlation: Correlate errors across distributed systems to find root causes.
Use Case: When you encounter a production error, this Skill can help identify the root cause by analyzing logs and stack traces.

Quick Start

Analyze the stack trace from the 'error-stacktrace.txt' file for patterns and anomalies.

Frequently Asked Questions about error-detective

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

FAQPage Schema

How do I find the root cause of a production error from a stack trace?▼

To find the root cause of a production error, you analyze stack traces and log files to identify error patterns and anomalies. This process correlates errors across distributed systems to pinpoint the underlying issue.

What is the best way to analyze log anomalies across distributed systems?▼

Analyzing log anomalies across distributed systems involves searching logs for specific error patterns and correlating them to identify a root cause. This process requires using regex patterns for error extraction and log analysis platforms.

Does this error detection approach work with Elasticsearch and Splunk?▼

Yes, this error detection approach works with Elasticsearch or Splunk. These platforms are used for log analysis, allowing you to search for specific error patterns and anomalies to diagnose issues across your systems.

How do I extract error patterns from a text file containing a stack trace?▼

To extract error patterns from a stack trace text file, you use regex patterns for error extraction. The analysis detects patterns and anomalies within the file contents across different programming languages.

When do I need regex patterns for error detection and root cause analysis?▼

You need regex patterns for error detection when searching logs and codebases for specific error patterns. They are required to extract anomalies from log data, which is then correlated to identify the root cause of system issues.