skills.rest
htlin222
htlin222COMMUNITY
Explore all skills by this author →
Website𝕏@htlin222GitHub

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

77|4|Updated Jun 20, 2022
Search Tags:#debugging#troubleshooting#stack trace#error analysis#production errors#log parsing
One-click install
npx skills add https://github.com/htlin222/dotfiles --skill error-detective-htlin222
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-detective
Source: https://github.com/htlin222/dotfiles/tree/main/claude.symlink/skills-archive/error-detective
Command: npx skills add https://github.com/htlin222/dotfiles --skill error-detective-htlin222

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you quickly identify, analyze, and understand the root causes of errors and anomalies within logs and codebases, significantly speeding up the debugging process.

Core Features & Use Cases

  • Log Analysis: Efficiently search and filter logs for specific error messages, patterns, and time ranges.
  • Stack Trace Parsing: Extract and interpret detailed stack traces to pinpoint the origin of exceptions.
  • Pattern Detection: Identify recurring errors and correlate them across different systems or requests.
  • Use Case: When an API is suddenly returning 500 errors, use this Skill to search logs for the specific error messages and stack traces, identify the faulty code path, and suggest a fix.

Quick Start

Search the application logs for any errors that occurred in the last hour and display the 10 most recent ones.

Frequently Asked Questions about error-detective

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

FAQPage Schema
How do I analyze production logs for stack traces and error patterns?▼

To analyze production logs, search and filter log files for specific error messages and time ranges, extract detailed stack traces to pinpoint exception origins, and detect recurring error patterns across various data sources to accelerate debugging.

What is the best way to debug sudden 500 errors from an API?▼

Debug sudden 500 errors by searching application logs for specific error messages and stack traces, identifying the faulty code path through pattern detection, and correlating anomalies to understand the root cause of the production failure.

How do I parse stack traces to find the origin of an exception?▼

Parse stack traces by extracting and interpreting detailed trace data to pinpoint the exact origin of exceptions within your codebase, which aids in understanding the root causes of errors and anomalies during debugging.

Can I correlate recurring errors across different systems using log analysis?▼

Yes, you can correlate recurring errors across different systems by running correlation queries across various data sources. This pattern detection identifies anomalies and helps pinpoint the root cause of issues during troubleshooting.

Do I need to provide specific time ranges when searching logs for anomalies?▼

Providing specific time ranges is supported and recommended for efficient log analysis. Filtering logs by time range helps you quickly isolate production errors, search for specific error patterns, and identify anomalies within a targeted window.

Related Skills

Explore More Software Engineering Skills→
albertdobmeyeralbertdobmeyer
2

log-analyzer

Analyze application logs to surface errors, exceptions, and root causes.

Community
Intermediate
fmflurryfmflurry
171

runtimeerror-http-localhost-error-resolution

Identify and resolve recurring runtime errors with a structured error-resolution pattern.

Community
Intermediate
89jobrien89jobrien
4

debugging

Parse logs and analyze stack traces to diagnose errors across languages.

Community
Advanced
latestaiagentslatestaiagents
5

log-forensics

Analyze application logs to identify issues, trace request flows, and detect anomalies.

Official
Advanced