← ClaudeAtlas

starter-session-auditlisted

Use when the user asks to audit a session for uncaptured learnings. Activates on "audit this session", "session audit", "what did we miss", "end of session check", or "/starter-session-audit". Scans the conversation for corrections, preferences, decisions, and new context, then proposes where to save each.
Sagargupta16/claude-skills · ★ 3 · AI & Automation · score 74
Install: claude install-skill Sagargupta16/claude-skills
# starter-session-audit A lightweight end-of-session audit. 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 things: 1. **Scans the conversation for uncaptured learnings** -- corrections, preferences, decisions, and new context that are not already in the project's instruction files. 2. **Proposes where to save each finding** -- which file, which section, exact wording. The user approves or skips each one. No file reorganization. No cleanup. No progress tracking. Just: "Did I learn anything this session that should be remembered?" ## Step 1: Discover the persistence layout Claude Code sessions can use several layers of persistence. Load whichever files exist: - **Project CLAUDE.md** -- at repo root or workspace root (standing instructions for this project). - **User-global CLAUDE.md** -- typically `~/.claude/CLAUDE.md` (preferences that apply everywhere). - **Memory / MEMORY.md** -- any workspace-level memory index file plus any topical files it points at. - **Live-state files** -- STATUS.md, TODO.md, or similar workspace files if the project uses them. - **Local-only override** -- `CLAUDE.local.md` (git-ignored, machine-specific). - **Rules** -- `.claude/rules/*.md` if the project uses path-scoped rule files. - **Resources** -- `.claude/resources/*.md` if the project keeps task-triggered reference docs. - **Repo-level CLAUDE.md** files in any repo to