Extract structured error reports from AI conversation context and save them as markdown files.
npx skills add https://github.com/gyy0592/claude-config --skill error-log
Please help me install this Agent Skill. Skill: error-log Source: https://github.com/gyy0592/claude-config/tree/main/skills/error-log Command: npx skills add https://github.com/gyy0592/claude-config --skill error-log
Conversations with AI can hide recurring failure modes because individual mistakes vanish once the exchange ends; this Skill captures each clear mistake as a structured, persistent data point so patterns can be analyzed and systemic fixes applied.
Invoke /error-log or say "log this error" to generate, review, and save a structured markdown error report to the default ~/.claude/error-logs/ directory.
High-intent search queries and answers about installing and using this skill.
To log AI mistakes during a conversation, you can invoke /error-log or express clear frustration. The system analyzes context to extract timestamp, model, task, category, trigger, expected vs actual behavior, root cause, and severity, generating a structured markdown report for your confirmation before saving.
Structured error logging for AI incidents captures model mistakes as persistent data points using a six-category classification. It records metadata including ISO timestamps, triggers, root causes, and fixes, preventing individual failures from vanishing when a conversation ends so patterns can be analyzed.
You can save an incident report for a Claude AI error by triggering the logging function, reviewing the automatically extracted diagnosis, and confirming the write. The report is appended to a markdown file in a configurable directory, defaulting to ~/.claude/error-logs/, using a strict filename convention.
Yes, you can automatically capture an audit trail when an AI makes a destructive action. The logging mechanism activates on explicit invocation or clear user frustration, extracts the root cause and expected versus actual outcomes, and stores the report append-only to preserve the incident history.
Yes, error logging works without requiring additional dependencies. It operates natively within the conversational session by analyzing existing context and metadata to generate the structured report, requiring only user confirmation before writing the markdown file to the local directory.
A limitation of automated AI error diagnosis is that it requires user confirmation before writing the report, meaning it cannot save logs fully autonomously. Additionally, it relies on analyzing conversation context, so it only captures mistakes that occur within the current interactive session.
openbotxStore and retrieve long-term facts and event logs for AI agents.
posit-devAnalyze incident logs and post-mortems to identify recurring failure patterns.
hariprasath-dlhAutomate incident response with anomaly detection, root cause analysis, and code fixes.
Soham407Convert AI-generated code into markdown deep-dive explanations by component and timestamp.
