memory-audit

memory-audit

Sibling of review — same flow, but scoped to the memory tree (~/.claude/projects/<slug>/memory/) instead of code.

When to run

• User types /memory-audit (explicit trigger).
• User says "check my memory for drift," "audit my notes," "are there stale references."
• Scheduled run via /schedule — weekly cadence is a natural fit (see "Schedule offer" below).
• Do not auto-fire on session start, post-capture, or any hook. Mode A only.

Inputs

1. Audit scope.
   • Default: ~/.claude/projects/<current-project-slug>/memory/. Resolve the slug the same way discover does (Glob ~/.claude/projects/*/memory/MEMORY.md, pick by project-root match).
   • --project <slug> → audit a specific other project's memory tree. Useful for cross-project hygiene.
   • --check <dimension> → run only one dimension (skip the others). Dimensions named below.
2. No content arguments — audit consumes the existing memory tree, not new content.

Procedure

1. Inventory the tree

Build the working set:

• Glob <memory-root>/**/*.md — every memory file plus session-recaps.
• Read <memory-root>/MEMORY.md — the index.
• For each memory file: parse frontmatter (name, description, type, kind, scope, relevance, relations, superseded_by); capture the body's first paragraph for duplicate detection. Batch the Reads — independent files in one message, not one call per file.
• For session-recap files (under sessions/<date>-<slug>.md): parse filename and frontmatter only; bodies are not scanned for content checks.

Build maps:

• path → frontmatter for every file.
• MEMORY.md line → target path for every index entry.
• path → list of incoming relations (computed by reverse-walking every file's relations: field — used for orphan detection in dimension 6).

If the inventory pass fails on any file (parse error, malformed frontmatter), surface that as the first finding under dimension 2 and continue with what parsed. Don't abort the whole audit because one file is broken.