session-mergelisted

# session-merge Replaces a ritual prompt that otherwise gets pasted verbatim into every parallel chat ("I need to combine some different claude code chats into one... add what we made in this chat as a block to this file"). ## Protocol 1. **Target file:** the path given; else look for an obvious existing one (`combine-notes.txt`, `combine-notes.md`) in repo root or cwd; else create `.claude/combine-notes.md`. 2. **Append one block** (never rewrite others' blocks): ```markdown --- ## Session <short-id> — YYYY-MM-DD — <one-line theme> **Built/changed:** <artifacts with real paths — files, skills, scripts, PRs> **Docs written:** <paths> **Key decisions:** <the 2-5 that a merger needs, with the why in one clause each> **Ideas worth keeping:** <unbuilt but valuable> **Open threads:** <what this session left unfinished> **Next steps:** <numbered, concrete> ``` 3. Session id: derive a short identifier from the transcript/session context if available; else date + theme slug. The block must make sense to a reader who never saw this chat. 4. Be selective — the merger reads many blocks; include what changes their decisions, drop process narration. 5. Confirm with the block's heading line only.