session-recalllisted

# Session recall: use sessionwiki as long-term memory The user's machine has a `sessionwiki` index of every past Claude Code, Codex, and Gemini CLI session. Treat it as the agent's long-term memory. It is local and offline - no network. Before solving something from scratch, check whether it was already solved. ## When to recall - Starting a non-trivial task -> search for prior work on the same topic first. - The user references earlier work ("the auth flow we built", "last week", "that CORS fix") -> recall it instead of asking them to re-explain. - You need to know which session changed a file -> trace it. ## How to recall (run these, do not guess) 1. **First time only**, confirm the tool exists: ``` command -v sessionwiki ``` If it prints nothing, the tool is not installed - see "If sessionwiki is missing" below and stop using this skill for the rest of the turn. 2. **Search prior sessions** on the task topic: ``` sessionwiki search --json "<topic keywords>" ``` Returns an array of hits: `id`, `tool`, `project`, `started`, `role`, `snippet`. Pick the 1-3 most relevant `id`s. 3. **Pull context** from a promising session before acting: ``` sessionwiki brief --json <id> ``` Returns the session's title, project, date, and a budgeted markdown transcript. Read it; carry forward decisions, file names, and gotchas. Do not re-derive what the prior session already settled. 4. **Trace a file** to the sessions that touched it, ne