session-review skill - Run at the end of the session to make sure you permanently learn everything new that came up in the session

SKILL.md

name	session-review
description	Reviews the current session and saves useful knowledge to the right documentation files in the current repo. Invoked via /session-review at the end of a working session. Captures new workflows, corrects outdated facts, and identifies documentation gaps. Discovers which files to update by reading this repo's AGENTS.md / CLAUDE.md — no hardcoded paths. Never saves to agent-specific memory — always saves to repo files.
disable-model-invocation	true

Session Review

Review the conversation and save useful knowledge to the right repo files. Knowledge lives in repo files, not agent-specific memory.

Step 1: Discover the Repo Documentation Map

Before scanning the conversation, read this repo's top-level AGENTS.md or CLAUDE.md (whichever exists). That file describes:

• What documentation files exist and what each covers
• Folder structure and conventions
• Any repo-specific rules about where knowledge is stored

If the repo contains sub-folder AGENTS.md files, read the ones relevant to what was worked on this session. Use the documentation map from those files — do not assume or hardcode file paths.

Step 2: Scan the Conversation

Once you know the repo's doc structure, scan the conversation for:

1. New workflows — Step-by-step procedures discovered or refined during the session
2. Corrected facts — Anything in existing docs found to be wrong or outdated
3. New reference details — Identifiers, types, mappings, or configurations discovered from real data
4. Naming/structure conventions — File naming patterns, folder layout decisions, and their rationale
5. Tool or integration notes — How specific tools, APIs, or services behave in this repo's context
6. Documentation gaps — Information useful for future sessions not yet documented anywhere

Step 3: Present Findings Before Writing

Group findings into three categories, then ask for confirmation:

Corrections

Facts found to be wrong in existing docs. Show old value -> new value and target file.

Additions

New knowledge not yet in any doc. For each: proposed destination file (from the discovered doc map) and exact text to add.

Gaps (suggestions only)

Information that would be useful but isn't yet collected. Suggest what to find and where to store it. Do not write these — just surface them.

Present all findings before writing anything. Ask: "Should I apply these changes? You can approve all, select specific ones, or skip."

Writing Rules

• Only write to files in this repo
• Use the documentation map discovered from AGENTS.md / CLAUDE.md to determine the right destination — do not infer paths independently
• Prefer editing existing files over creating new ones
• Extend existing sections rather than duplicating content
• After writing, list every file changed and what was added/corrected