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
CipherClaw: Using a Security Persona to Audit Code with Claude
A developer used CipherClaw, a CLAUDE.md persona called TALON, to make Claude Code think like a security architect. Running it on a Next.js app revealed 17 security findings including critical vulnerabilities like unauthenticated endpoints returning admin data and hardcoded auth tokens.
Benchmark shows context engine reduces AI coding agent costs by 3x on SWE-bench
A benchmark of 4 coding agents using Claude Opus 4.5 on SWE-bench Verified shows a context engine achieved 73% pass rate at $0.67/task, while other agents cost up to $1.98/task for similar or lower performance.
Claude AI Opus Disables Intel DPST Auto-Dimming by Editing Registry in 0002 Key
A Reddit user automated the fix of Intel Display Power Saving Technology dimming by letting Claude AI Opus edit the registry — it found the correct FeatureTestControl value and key location.
Monarch v3: NES-Inspired KV Paging for 78% Faster LLM Inference
Monarch v3 implements NES-inspired memory paging for transformers, achieving 78% faster inference (17.01 to 30.42 tok/sec) on a 1.1B parameter model with nearly zero VRAM overhead. The open-source algorithm splits KV cache into hot and cold regions with compression and promotion mechanisms.