failure-log-manager

Failure Log Manager

Manages the persistent failure log at .claude/failure-log.local.md to prevent repeating mistakes across sessions.

Activation Triggers

This skill activates when:

• User asks to log a mistake or failure
• A pattern violation or error is detected
• User wants to review known mistakes
• Adding, viewing, or managing failure entries

File Location

.claude/failure-log.local.md

This file is project-specific and should be in .gitignore.

File Format

---
enabled: true
last_updated: 2026-01-01T10:30:00Z
---

# Failure Log

## Pattern Mistakes

### [YYYY-MM-DD] Brief title
**Context:** What was being done
**Mistake:** What went wrong
**Correct:** What should be done instead
**Category:** imports|security|testing|architecture|conventions

## Failed Approaches

### [YYYY-MM-DD] Brief title
**Context:** What was being attempted
**What failed:** Why the approach didn't work
**Better approach:** What works instead
**Category:** imports|security|testing|architecture|conventions

Categories

Category	Description	Examples
imports	Wrong import patterns	Relative imports, missing aliases
security	Missing security checks	No permission classes, exposed secrets
testing	Wrong test approaches	unittest vs pytest, missing fixtures
architecture	Structural mistakes	Wrong file locations, missing layers
conventions	Code style violations	Naming, formatting, patterns

Adding Failures

Pattern Mistake Entry

For recurring pattern violations:

### [2026-01-01] Wrong import pattern in Django
**Context:** Writing user service
**Mistake:** Used `from users.models import User` instead of alias pattern
**Correct:** Use `import users.models as _users_models`
**Category:** imports

Failed Approach Entry

For approaches that don't work:

### [2026-01-01] Tried unittest instead of pytest
**Context:** Writing tests for user service
**What failed:** unittest assertions don't integrate with Django fixtures
**Better approach:** Use pytest with factory_boy for test data
**Category:** testing