memory-review

1# Memory Review
2 
3Curate the user's file-based agent memory: the long-form CLAUDE.md files plus
4the per-project auto-memory store — read through the Agent Monitor dashboard at
5`http://localhost:4820`.
6 
7## Input
8 
9The user provides: **$ARGUMENTS**
10 
11This may be:
12- empty — review the whole memory store across every project (default).
13- a project slug (e.g. `-Users-david-WebstormProjects-foo`) — restrict the
14  review to that one project's auto-memory dir.
15- "claude-md" — review only the user/project CLAUDE.md files.
16 
17## Data Sources
18 
19| Endpoint | Returns |
20|----------|---------|
21| `GET /api/cc-config/memory` | `{ items:[…] }`. CLAUDE.md entries: `{ scope:"user"\|"project", file, size, mtime, preview }`. Auto-memory entries: `{ scope:"auto-memory", project, name, isIndex, file, size, mtime, frontmatter, preview }` |
22| `GET /api/cc-config/file?path=<abs>` | full body of one file: `{ ok, file, size, mtime, truncated, text }` — use to read a fact in full before recommending an edit |
23 
24## Report Sections
25 
26### 1. CLAUDE.md overview
27List the user and project CLAUDE.md entries with `scope`, `size` (KB), and
28last-modified (`mtime`). Note any that are `truncated` (over 256 KB) — these
29are oversized and worth splitting into auto-memory facts.
30 
31### 2. Per-project auto-memory, grouped
32Group `scope: "auto-memory"` items by `project`. For each project show the
33**index** (`isIndex: true`, typically `MEMORY.md`) first, then the per-fact
34…