Audit Memory

Saved memories are point-in-time observations. Code moves, PRs merge, projects finish — and a memory that was true when written silently becomes a confidently wrong instruction to every future session. This skill verifies memories against reality and archives what no longer holds.

Never auto-fires — it archives user data, so it runs only when someone types /audit-memory.

Core guarantees

These are load-bearing. Violating any of them makes the skill untrustworthy:

Absence of evidence is never evidence of staleness. A claim you cannot check is NEEDS-<tool>, NOT-ATTEMPTED or NOT-CHECKABLE — never stale, never offered for removal. A disconnected MCP must never turn valid memories into deletion candidates. Two mirrors of this also hold. Never report a check you skipped as a tool that was missing. And never over-apply it: a newer memory stating the old fact was removed is positive evidence, sufficient alone — an unreachable repo cannot demote it, because the evidence was never in the repo.
Archive before you touch anything, so nothing is unrecoverable. Memory files are not version-controlled and have no trash. Snapshot the original into the archive before any write or removal — claim removals, whole-file archiving, MEMORY.md pointer sync, and lastReviewed stamps alike. Removal does mean deleting the file; it is safe only because the verified snapshot precedes it.
Preferences are not claims. type: feedback and type: user memories are standing instructions. Never argue they are false — the user is the only authority on whether a preference still applies.
No writes outside the resolved roots. Only the memory root and archive root are ever written to.
Name the root you actually audited, before showing findings, and never claim you honoured CLAUDE_MEMORY_ROOT unless you read it. Auditing a different corpus than the caller meant is the worst failure here.

Step 1 — Resolve roots and discover projects

Run this exactly as written, as a single call. It resolves both roots and lists every project in one step.