claude-continuationlisted

# claude-continuation Two halves of one loop: - **End** — capture what was done and what to do next, to `.claude/continuations/`. - **Continue** — read the latest handoff back and orient against live repo state. Pick the half that matches the request. Never run both in one go. --- ## End a session ### Phase 1 — Capture state 1. **Project name:** `basename "$(git rev-parse --show-toplevel)"`, else `basename "$(pwd)"`. 2. **Git state** (skip if not a repo): `git rev-parse --abbrev-ref HEAD`, `git status --short`, `git log --oneline -5`, `git diff --stat`. 3. **Conversation review:** what was completed (files, features, fixes), what's unfinished, any non-obvious gotchas or decisions, and the session topic in 2–4 words for the filename slug. ### Phase 2 — Draft and confirm Draft the file inline in chat first, filling every section concretely: ```markdown # {Project Name} — {Topic} **Session timestamp:** {YYYY-MM-DDTHH:MM:SS} **Branch:** {branch-name, or "—" if non-git} ## What was done this session - {Concrete bullet} ## Current state - **Working:** {what runs/passes} - **Not yet:** {what's incomplete} - **Uncommitted changes:** {summary from git status, or "none"} ## Next task {One clear, unambiguous instruction. Specific enough to start without re-asking.} ## Key files - `path/to/file` — why it matters ## Notes {Optional. Skip the heading entirely if nothing to add.} ``` Then, only if there is genuinely non-obvious material, draft a learnings block: ```m