Fixing Context Bloat in Claude Code Auto-Memory with a Naming Schema and Audit Script
A developer on r/ClaudeAI shared a practical skill that addresses memory drift and context bloat in Claude Code's auto-memory after months of use. The skill enforces file naming, required frontmatter fields, and includes a bash audit script to detect issues.
What the Skill Does
Claude Code auto-memory (v2.1.59+) writes plain markdown to ~/.claude/projects/<slug>/memory/. The skill adds structure on top: files follow <type>_<topic>.md naming, require name, description, type in frontmatter, and feedback entries must include a Why section. Auto-memory still writes; the skill makes Claude write to the spec.
Key Features
- Phrase-triggered review: Say "Audit memory" to run the audit script; "Review session" walks the recent session and surfaces what to keep.
- Soft warning: Audit reports drift but does not block writes.
- Plain markdown: Files remain editable with grep, git, etc. No database or daemon.
Effect on Memory
One topic per file means Claude lands on the right entry on first lookup. A deduplicated library loads fewer files per session, freeing context for the work itself.
Sample Audit Output
Memory audit · 2026-05-15 · 132 files Hard checks (must be zero): missing frontmatter 0 frontmatter fields 0 feedback missing Why 1 naming violations 0 broken MEMORY.md links 0 Soft signals: oversized files 78 groups over 15 entries 3 untouched 30+ days 31 not in MEMORY.md 0 Hard-rule compliance: 99.2% (1 violation / 132 files)
Installation
Paste into any Claude Code session: Install the claude-memory-manager skill from https://github.com/jau123/claude-memory-manager. Then say "audit memory" to verify.
Comparison with Built-in Auto-Memory
- Auto-memory alone: No schema, no audit. Claude decides naming and structure.
- With this skill: 3-type schema + required fields + Why on feedback + one-command audit script.
Limits
- Single-project scope only.
- No semantic ranking — audit is pattern matching only.
- Bash script; Windows/git-bash untested.
- Overkill for small libraries (under ~10 entries or 1 month).
📖 Read the full source: r/ClaudeAI
👀 See Also
Coordinator Server for Multi-Agent Development Prevents Overwrites
A developer built a Node.js coordinator server that manages line-range locking, line shift tracking, and real-time messaging between AI agents working on the same codebase. The system prevents agents from overwriting each other's work by using HTTP-based locking with conflict detection.
A 4-tier knowledge base architecture to improve AI agent accuracy
A developer built a structured knowledge base with 200+ articles to provide domain-specific context to AI agents, implementing a 4-tier pipeline with query classification that cut token costs by ~40%.
No-Code Persistent Memory System for Claude Using Notion and MCP
A radiologist built a 'Cognitive Hub' in Notion that Claude reads and writes to through MCP, creating a structured knowledge base with a routing table to load only relevant information per conversation. The system has grown to 70+ pages after a month of daily use.
Phalanx CLI coordinates multiple AI agents for automated code-review cycles
A developer built Phalanx, a CLI tool that coordinates AI agents from different providers: Codex handles coding, Claude Opus performs code review, and Claude Sonnet orchestrates the loop. A companion tool called Codebones compresses repositories to structural maps to reduce token usage.