How does a mistake become a guardrail?

The skill uses a 14-day review period. If a mistake occurs twice in the same repo within 14 days, it is promoted to a 'Hot Rule' in that repo's agent file.

Does it clean up old or unnecessary rules?

Yes, if 14-30 days pass without a specific mistake occurring, the demotion procedure proposes removing the associated one-line guardrail to keep files clean.

Where are the mistakes logged?

Mistakes are stored in two locations: a global log at ~/.claude/mistakes.jsonl and a project-specific log at /memory/mistakes.jsonl.

What kind of mistakes can be tracked?

It can track any procedural error, including skipping pre-flight checks, unauthorized port closures, or failing to consult documentation before executing tasks.

Mistake Tracking & Guardrail Management

Name: Mistake Tracking & Guardrail Management
Author: mshuffett

bymshuffett

Analytics & Monitoring

Logs recurring AI errors and automatically promotes or demotes guardrails based on frequency to improve model reliability.

About

The Mistake Tracking skill implements a systematic feedback loop for Claude, allowing it to record, analyze, and learn from its own procedural errors. By logging events into structured JSONL files at both global and project levels, the skill provides a data-driven method for managing 'Hot Rules.' It features a built-in promotion and demotion logic that converts frequent mistakes into hard guardrails while pruning unnecessary rules during periods of high performance, ensuring Claude adapts to your specific repository constraints and workflows without manual intervention.

Key Features

Automated promotion of recurring errors into project Hot Rules
Mandatory guide consultation enforcement for high-risk procedural tasks
Rule demotion logic to prevent instruction bloat during quiet periods
Pre-defined event schema for structured mistake auditing
Dual-level logging in global and project-specific JSONL files
0 GitHub stars

Use Cases

Enforcing strict adherence to internal documentation and acceptance checks
Self-optimizing Claude's guardrails based on 14-30 day performance cycles
Reducing recurring git and environment errors in complex monorepos

About

Key Features

Automated promotion of recurring errors into project Hot Rules
Mandatory guide consultation enforcement for high-risk procedural tasks
Rule demotion logic to prevent instruction bloat during quiet periods
Pre-defined event schema for structured mistake auditing
Dual-level logging in global and project-specific JSONL files
0 GitHub stars

Use Cases

Enforcing strict adherence to internal documentation and acceptance checks
Self-optimizing Claude's guardrails based on 14-30 day performance cycles
Reducing recurring git and environment errors in complex monorepos