# Record Project Errors for Future Runs

Repeated assistant mistakes slow down development and reduce trust. This skill turns each mistake into a compact local rule for future work.

## Install

```bash
npx skillstore add aceek/error-memory
```

## Metadata

- - Status: approved
- - Slug: aceek-error-memory
- - Version: 1.0.0
- - Author: Aceek
- - GitHub username: Aceek
- - License: MIT
- - Repository: https://github.com/Aceek/claude-config/tree/master/src/skills/error-memory
- - Ref: master
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: filesystem
- - Quality score: 77
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/aceek-error-memory
- - Manifest: https://skillstore.pages.dev/api/skills/aceek-error-memory/manifest

## Capabilities

- Classifies mistakes as technical, context, or comprehension errors.
- Guides root cause analysis after failures or user corrections.
- Defines a compact Markdown table format for reusable error rules.
- Instructs assistants to append new entries to .claude/errors.md.
- Provides a starter template when the local error log is missing.

## Use Cases

- Prevent Repeated Build Failures: Capture the cause of a failed build and define a rule before the next change.
- Preserve Project Conventions: Record corrections about local patterns, file layout, or tooling choices.
- Improve Assistant Handoffs: Keep a concise mistake log that later Claude, Codex, or Claude Code sessions can inspect.

## Prompt Templates

### Record a Simple Mistake

```
I made a mistake in this project. Classify it, find the root cause, and add one concise rule to the error log.
```

### Capture a User Correction

```
The user corrected my approach. Turn the correction into a context rule and append it to .claude/errors.md.
```

### Analyze a Failed Change

```
Tests failed after my last change. Identify the root cause, separate symptoms from cause, and record the prevention rule.
```

### Review Before Complex Work

```
Before starting this task, review the existing error log and explain which prior rules affect the implementation plan.
```

## Limitations

- It does not automatically detect errors without assistant judgment.
- It writes project notes only when the assistant follows the process.
- It does not sync error memory across repositories.
- Sensitive project details may be recorded if users do not review entries.

## Best Practices

- Review each entry before storing sensitive project details.
- Keep every rule short, specific, and directly actionable.
- Check the error log before making high-risk project changes.

## Anti Patterns

- Do not record vague excuses instead of root causes.
- Do not store secrets, credentials, or private user data.
- Do not let the error log grow without archiving old entries.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T04:41:13.256\+00:00
- - Summary: The external command, weak cryptography, and reconnaissance findings are false positives from Markdown content in SKILL.md. The skill does instruct the assistant to append or create a local .claude/errors.md file, so it has low filesystem persistence risk.

## Stats

- - Views: 192
- - Downloads: 14
- - Favorites: 0
- - Popularity score: 0