skills.rest
dudusoar
dudusoarCOMMUNITY
Explore all skills by this author →
GitHub

error-logger

Create structured ERROR_LOG.md entries documenting debugging knowledge.

4|Updated Dec 31, 2025
Search Tags:#debugging#root-cause#error-patterns#error-logging#log-entries#knowledge-extractor
One-click install
npx skills add https://github.com/dudusoar/skillOS --skill error-logger-dudusoar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-logger
Source: https://github.com/dudusoar/skillOS/tree/main/.claude/skills/error-logger
Command: npx skills add https://github.com/dudusoar/skillOS --skill error-logger-dudusoar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tactical debugging knowledge is scattered and hard to reuse; this skill ensures a structured ERROR_LOG.md that captures errors, root causes, solutions, and prevention strategies to accelerate debugging and learning across projects.

Core Features & Use Cases

  • Maintains ERROR_LOG.md with detailed entries for errors, bugs, and debugging sessions.
  • Distinguishes tactical debugging knowledge from strategic project logs (LOG.md) and links to extraction processes.
  • Triggers: encountering an error, a tricky debugging session, or identifying recurring patterns that warrant a documented entry.

Quick Start

Log an error event by creating a new entry in .claude/ERROR_LOG.md following the 8-step workflow.

Frequently Asked Questions about error-logger

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

FAQPage Schema
How do I document debugging sessions with structured error logs?▼

Structured error logging distinguishes tactical debugging knowledge from strategic project logs (LOG.md) by capturing recurring issues, edge cases, and root causes. It links documented errors to a knowledge-extractor process to accelerate reuse across projects.

How do I structure error log entries for recurring project issues?▼

Use an error-type taxonomy to structure log entries by classifying error context, messages, and root causes. The 8-step workflow ensures consistent documentation from initial identification through implemented solution and prevention strategy.

What's the best way to capture root cause analysis results from debugging?▼

Capture root cause analysis by documenting the debugged issue, its classification, and prevention strategy within structured ERROR_LOG.md entries. The workflow links these tactical debugging records to knowledge extraction for accelerating future problem solving.

When should I create an error log entry instead of a general project log?▼

Create an error log entry when encountering errors, tricky debugging sessions, or recurring edge cases requiring tactical knowledge capture. Reserve general project logs for strategic entries, maintaining a clear separation between tactical debugging and high-level project tracking.

Related Skills

Explore More Software Engineering Skills→
sebmartinsebmartin
4

init

Create threads directory, .claude/settings.json, and CLAUDE.md scaffolding.

Community
Intermediate
wangke19wangke19
1

session-postmortem

Convert completed software tasks into reusable patterns, playbooks, and automation components.

Community
Advanced
carson-sweetcarson-sweet
6

Product Competition

Consolidate strategic positioning and feature-level comparisons into a unified competitive analysis workflow.

Community
Advanced
terrylicaterrylica

mt5-log-reader

Parse MetaTrader 5 log files to validate execution and surface errors.

Community
Intermediate