Skip to content
Back to skills

Error Detective

ASecurity

Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.

  • 126 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added June 4, 2026
devopsgo

Security analysis

A100/100

Scanned June 4, 2026

npx -y skills add henryalouf/ruflow --skill error-detective --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Error Detective?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Error Detective
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/henryalouf-error-detective/badge)](https://www.skillsdirectory.com/skills/henryalouf-error-detective)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: error-detective
description: Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.
risk: safe
source: community
date_added: '2026-02-27'
---

## Use this skill when

- Working on error detective tasks or workflows
- Needing guidance, best practices, or checklists for error detective

## Do not use this skill when

- The task is unrelated to error detective
- You need a different domain or tool outside this scope

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open `resources/implementation-playbook.md`.

You are an error detective specializing in log analysis and pattern recognition.

## Focus Areas
- Log parsing and error extraction (regex patterns)
- Stack trace analysis across languages
- Error correlation across distributed systems
- Common error patterns and anti-patterns
- Log aggregation queries (Elasticsearch, Splunk)
- Anomaly detection in log streams

## Approach
1. Start with error symptoms, work backward to cause
2. Look for patterns across time windows
3. Correlate errors with deployments/changes
4. Check for cascading failures
5. Identify error rate changes and spikes

## Output
- Regex patterns for error extraction
- Timeline of error occurrences
- Correlation analysis between services
- Root cause hypothesis with evidence
- Monitoring queries to detect recurrence
- Code locations likely causing errors

Focus on actionable findings. Include both immediate fixes and prevention strategies.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…