Error Logging
Log all errors with full context, detect patterns, and suggest approach mutations to avoid repeated failures.
Best use case
Error Logging is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Log all errors with full context, detect patterns, and suggest approach mutations to avoid repeated failures.
Teams using Error Logging should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/error-logging/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Error Logging Compares
| Feature / Agent | Error Logging | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Log all errors with full context, detect patterns, and suggest approach mutations to avoid repeated failures.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Error Logging Log all errors with full context, detect patterns, and suggest approach mutations to avoid repeated failures. ## Agent Error Analyst - `pwf-error-analyst` ## Workflow 1. Log ALL errors immediately to progress.md (Rule 3) 2. Include error context, stack traces, and reproduction steps 3. Tag errors with severity: critical, warning, informational 4. Analyze error patterns across phases and iterations 5. Suggest approach mutations for known failure patterns (Rule 4) 6. Track error resolution status for verification ## Inputs - `projectPath` - Root path for planning files - `phaseName` - Phase where error occurred - `errors` - Array of error objects - `errorHistory` - Previous errors for pattern detection ## Outputs - Updated progress.md error section - Approach mutations with alternative strategies - Error resolution report for verification ## Process Files - `planning-orchestrator.js` - Error logging during phases - `planning-execution.js` - Immediate error logging, pattern analysis - `planning-verification.js` - Error resolution checking
Related Skills
error-code-catalog
Manage and document SDK error codes and messages
actionable-error-formatter
Format errors with actionable fix suggestions and documentation links
Error Messages
Expert skill for designing and implementing high-quality compiler error messages
mitiq-error-mitigator
Error mitigation skill using Mitiq for NISQ device noise reduction
logging-migrator
Migrate logging infrastructure with format standardization, structured logging, and aggregation setup
mcp-error-code-mapper
Map application errors to MCP error codes with proper messages, error types, and recovery suggestions.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.