Agent skill · software engineering · aiskillstore
error-detective
Systematic debugging and error resolution using the TRACE framework (Trace, Read, Analyze, Check, Execute). Use when debugging errors, analyzing stack traces, investigating failures, root cause analysis, or troubleshooting production issues.
Why this skill is useful
Provides structured methodologies and specific error analysis techniques that the AI wouldn't reliably generate on its own.
What it needs
About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Error Detective - Systematic Debugging and Error Resolution Overview Error Detective is a comprehensive debugging skill that applies systematic methodologies to identify, analyze, and resolve errors efficiently. Using the TRACE framework and structured analysis techniques, this skill guides you through debugging from initial error discovery to verified resolution. Core Capabilities Stack Trace Analysis Parse and interpret stack traces across multiple languages Identify root cause vs. symptom errors Extract relevant file paths and line numbers Understand call chains and error propagation Error Pattern Recognition Categorize errors by type (syntax, runtime, logic, integration) Identify common error patterns and anti-patterns Recognize framework-specific errors Map errors to likely root causes Root Cause Analysis Distinguish between symptoms and underlying issues Follow error chains to original source Identify environmental vs. code issues Detect configuration and dependency problems Debugging Workflow Management Structured investigation process Hypothesis generation and testing Iterative refinement of understanding Documentation of findings and solutions The TRACE Framework TRACE is a systematic five-step approach to debugging any error: T - Trace the Error Objective: Capture complete error information and context 1. Collect the full error message Complete stack trace (not just first few lines) Error type and message Timestamp and occurrence frequency Environment where error occurred 2. Identify error location Exact file and line number Function or method where error occurred Code context (surrounding lines) Call stack from entry point to error 3. Gather reproduction steps Minimal steps to reproduce Input data or parameters used Expected vs. actual behavior Consistency of reproduction (always, intermittent, rare) R - Read the Error Message Objective: Extract all information from the error itself 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/error-detective