← ClaudeAtlas

memory-hygienelisted

Audit and clean up Claude Code's persistent memory system — MEMORY.md, memory files, lessons, and ADRs. Use this skill when: (1) the user asks to clean up, audit, or review their memory/lessons/ADRs, (2) MEMORY.md is approaching or exceeding the 200-line limit, (3) lesson files have grown large and may contain duplicates, (4) you notice ADR numbering conflicts, (5) memory files seem stale or contradicted by current code, or (6) the user says things like 'my memory is getting messy', 'clean up my lessons', 'deduplicate', 'review ADRs', 'memory audit'. Also proactively suggest running this after 10+ sessions on a project, or when MEMORY.md triggers a truncation warning.
wan-huiyan/claude-ecosystem-hygiene · ★ 0 · Data & Documents · score 70
Install: claude install-skill wan-huiyan/claude-ecosystem-hygiene
# Memory Hygiene v3.3 — Audit & Cleanup This skill audits Claude Code's persistent knowledge stores (axioms, MEMORY.md — both auto-memory and in-repo, memory topic files, lessons, phase templates, ADRs, and the project `docs/` taxonomy) for structural problems that degrade future session quality. It produces a structured report, gets user approval, then executes fixes. v3.3 adds **label-table integrity audit** (§1i) and **project `docs/` taxonomy audit** (§1j). The 7-bucket taxonomy that `session-handoff` dispatches to is now defined here as source-of-truth — previously `session-handoff` referenced "memory-hygiene v3.1" for this but the definition lived nowhere. §1i catches fabricated code→label tables in `lessons.md` / `feedback_*.md` / `reference_*.md` that bypass the author-side gate `session-handoff` runs in its Phase 0. v3.2 adds **in-repo `MEMORY.md` detection** (§1a2) — the A/B counterfactual harness (n=3, 2026-04-21) showed that in-repo `MEMORY.md` files (e.g., project-root `MEMORY.md` or `docs/MEMORY.md`) survive a `CLAUDE_CONFIG_DIR` clean env and drive measurable success on tasks that the `~/.claude/projects/*/memory/MEMORY.md` auto-memory file cannot. v3.1's §1a scanned only the auto-memory MEMORY.md, making the in-repo counterpart invisible to memory hygiene. v3.2 scans both and reports them as separate tiers in the audit output (T1 auto-memory and T1-repo). v3.1 added **feedback lifecycle detection** (§1c2) — classifying each `feedback_*.md` file as Incorpor