session-auditlisted

End-of-session audit that scans the conversation for corrections, preferences, decisions, and new context that were never saved, then proposes where each belongs in the user's memory files (CLAUDE.md, MEMORY.md, or a memory/ folder). Use whenever the user says "audit this session", "session audit", "what did we miss", "end of session check", or asks to capture what was learned before closing a session. Adapts to whatever memory structure the workspace already has, and proposes a simple one if none exists.
meggiepham06-smile/session-audit-skill · ★ 0 · AI & Automation · score 65

Install: claude install-skill meggiepham06-smile/session-audit-skill

# Session Audit A lightweight audit that runs at the end of a session. It catches things the user said during the session that should be saved permanently, so they never have to say them again. ## What this skill does Two things, and only two: 1. **Scans for uncaptured learnings.** Looks through the conversation for corrections, preferences, decisions, and new context that aren't already written in the workspace files. 2. **Proposes where to save each one.** For each finding, names the file, the section, and the exact wording. The user approves or skips each one. No file reorganization, no cleanup. Just: "Did we learn anything this session that should be remembered, and where does it go?" ## Step 1: Discover the workspace's memory structure Different workspaces store memory differently. Before scanning, find out what exists here: 1. Look for a root `CLAUDE.md` (standing behavior rules) and a root `MEMORY.md` (facts that change over time). 2. Look for a `memory/` folder with deeper files (for example `memory/people.md`, `memory/terminology.md`, or per-project subfolders). 3. Look for per-project `CLAUDE.md` / `MEMORY.md` files inside project folders that were worked on this session. Read every memory file that exists and was relevant this session. Note which of the three layers above are present; Step 4 adapts to what you found. If **no** memory files exist at all, don't fail. Run the scan anyway, and at the end offer to create a minimal structure: one `CLAUDE.md` fo