memory-auditlisted

# Memory Audit Walk the project's auto-memory directory and classify every entry indexed in `MEMORY.md`. The audit is read-only: it never moves, modifies, or deletes any file. Output is a markdown table plus a list of suggested `mv` commands the user can copy if they want to act on the recommendations. ## When to use - `MEMORY.md` has grown past ~25 entries and you suspect bloat. - A session-start drift hint named some entries as >30 days old. - Multiple `project_v*_shipped.md` files have accumulated (the v1.20.0 rule rewrite forbids these going forward, but old ones remain on disk). - A reviewer or oracle flagged a memory entry that no longer matches the source. ## When NOT to use - The directory is small and recently curated — the audit will produce a near-empty report. - You want to *make* the moves, not just see suggestions. The skill prints `mv` commands; review and run them yourself. - You want to audit a different project's memory than the one you are in. Pass `--memory-dir <path>` explicitly to point at another project's memory directory. ## Steps 1. Take any optional argument: - `--memory-dir <path>` — explicit memory directory to audit. Defaults to `${HOME}/.claude/projects/<dashed-cwd>/memory/` derived from the current working directory (matches Claude Code's project-memory convention). 2. Run the helper script: ```bash bash ~/.claude/skills/autowork/scripts/audit-memory.sh ``` Or with an explicit dir: ```bash bash ~/.claude/skills/au