Where are the learned error patterns stored?

All identified patterns and rules are stored in .claude/rules/error_rules.json, allowing for both automated updates and manual refinements.

Can I generate a summary of my recent coding errors?

Yes, you can run the provided analysis script with the --report flag to generate a detailed Markdown report of errors captured over the last 24 hours or a custom timeframe.

Does this skill provide automated fix suggestions?

It identifies recurring patterns and maps them to specific fix suggestions, such as recommending the correct Docker connection string for PostgreSQL failures.

Can it prevent me from running commands that usually fail?

Yes, the error-pattern-warner hook checks your commands against known failure patterns and issues a warning if you are about to run something that has historically caused issues.

How does this skill capture errors in Claude Code?

It utilizes a post-tool hook that automatically captures the tool name, error message, and input command whenever a tool fails, saving the data to a local JSONL log file.

Error Pattern Analyzer

Name: Error Pattern Analyzer
Author: yonatangross

byyonatangross

•

Analytics & Monitoring

Analyzes and troubleshoots recurring error patterns in Claude Code sessions to streamline debugging and prevent repeated failures.

About

The Error Pattern Analysis skill provides a robust framework for capturing, logging, and analyzing tool failures within Claude Code. By monitoring command outputs and maintaining a history of errors in a local JSONL log, it automatically identifies repeating patterns and generates actionable insights or proactive warnings. This skill is essential for developers looking to move beyond manual debugging, offering automated pattern recognition that suggests fixes for common environment issues, database connection errors, and risky command executions based on historical data.

Key Features

Pre-configured patterns for common PostgreSQL and environment failures
Automated rule generation based on recurring error signatures
Automated error collection from Bash and MCP tool executions
Proactive warning system that flags risky commands before execution
29 GitHub stars
Batch analysis of error logs with customizable timeframes and reporting

Use Cases

Identifying and resolving persistent database connection issues during development
Auditing daily coding sessions to detect and fix systematic tool failures
Creating custom warning rules for complex command sequences that are prone to failure

About

Key Features

Pre-configured patterns for common PostgreSQL and environment failures
Automated rule generation based on recurring error signatures
Automated error collection from Bash and MCP tool executions
Proactive warning system that flags risky commands before execution
29 GitHub stars
Batch analysis of error logs with customizable timeframes and reporting

Use Cases

Identifying and resolving persistent database connection issues during development
Auditing daily coding sessions to detect and fix systematic tool failures
Creating custom warning rules for complex command sequences that are prone to failure