← ClaudeAtlas

memory-gclisted

Interactive cleanup session for file-based agent memory. Runs a memgc scan, presents findings in groups, the user decides, the agent applies (archive/merge/fix-index/fix-frontmatter). Use when memory feels stale or the agent acts on outdated facts.
adrianfoehl/memory-metabolism · ★ 0 · AI & Automation · score 72
Install: claude install-skill adrianfoehl/memory-metabolism
# Memory garbage collection (interactive review) Principle: **the scanner finds, the user decides, the agent applies.** Nothing is deleted silently, superseded files are invalidated and archived with provenance. ## Paths (adapt to your setup) - memgc CLI: `<path-to>/memgc/` (run `uv run memgc …` there; config `memgc.yaml`) - Report: `<path-to>/memgc/reports/latest.json` - Archive convention per store: `<store>/archive/` + `archive/INDEX.md` ## What to do ### Step 1: Fresh scan + audit ```bash cd <path-to>/memgc && uv run memgc scan && uv run memgc audit ``` Show the audit head (always-loaded tokens = what steers every session). ### Step 2: Safety net For every store you will touch: is it a git repo with a clean state? If not: `git init` + baseline commit first. No writes without a safety net. ### Step 3: Present findings in groups Read `reports/latest.json`. Order: 1. **action findings** (index_diff, broken frontmatter), mechanical, fast 2. **review findings** (markers, near_duplicates, cross_store_drift, retention) 3. **stale_review** (reconsolidation): READ the file, check its claims against reality, then either correct it OR confirm it, in both cases bump `updated:`. 4. **contradiction_candidates / entity_staleness**: read the involved files yourself and judge semantically. Only present real contradictions, each with a quote from both sides and a concrete resolution proposal. Per group: compact summary + recommendation, then let the user decide (batch