ccc-save-sessionlisted

# /ccc-save-session — Save Session State Capture everything that happened in this session — what was built, what worked, what failed, what is left — and write it to a dated file so the next session can pick up exactly where this one left off. ## When to Use - End of a work session before closing Claude Code - Before hitting context limits (run this first, then start a fresh session) - After solving a complex problem you want to remember - Any time you need to hand off context to a future session ## Process ### Step 1: Gather context Before writing the file, collect: - Read all files modified during this session (use git diff or recall from conversation) - Review what was discussed, attempted, and decided - Note any errors encountered and how they were resolved (or not) - Check current test/build status if relevant ### Step 2: Create the sessions folder if it does not exist ```bash mkdir -p ~/.claude/sessions ``` ### Step 3: Write the session file Create `~/.claude/sessions/YYYY-MM-DD-<short-id>-session.tmp`, using today's actual date and a short-id that satisfies these rules: - Allowed characters: lowercase `a-z`, digits `0-9`, hyphens `-` - Minimum length: 8 characters - No uppercase letters, no underscores, no spaces Valid examples: `abc123de`, `frontend-worktree-1` Invalid examples: `ABC123de` (uppercase), `short` (under 8 chars), `test_id1` (underscore) Full valid filename example: `2024-01-15-abc123de-session.tmp` ### Step 4: Populate all sections Write e