--- name: wrap-up-session description: End-of-session wrap-up - capture context for continuity allowed-tools: - Read - Write - Edit - Glob - Grep - AskUserQuestion - "Bash(git *)" --- # Skill: Session Wrap-Up ## Purpose Capture session context for continuity when ending a work session (but the task/memory is not complete). ## When to Use - User says "wrap up", "done for now", "let's close out" - Ending work for the day but will continue later - Context-switching between tasks **Note:** If the memory/task itself is complete, use `/mem wrap-up` instead. ## Process ### Step 1: Identify Active Memory - Check conversation context for which memory was being worked on - If no active memory, just commit any outstanding changes and summarize ### Step 2: Update metadata.yaml Add/update session context (status stays as-is): ```yaml updated: YYYY-MM-DD last_session: date: YYYY-MM-DD summary: next_steps: - - ``` ### Step 3: Update notes.md Append session notes for continuity: ```markdown ## Session: YYYY-MM-DD ### What Was Done - - ### Where We Left Off - - ### Next Steps - [ ] ### Open Questions - ``` ### Step 4: Review Permission Escalations Check if any permissions were manually approved during the session that should be added to shared settings: ```bash # Look at settings.local.json for session-added permissions cat .claude/settings.local.json 2>/dev/null ``` If local overrides exist: 1. Show the user what's in local vs shared 2. Ask which should be promoted to `settings.json` 3. Apply changes and remove redundant local entries 4. If local becomes empty/redundant, delete it ### Step 5: Check for Skill Changes ```bash git status --short projects/*/skills/ ``` If skill changes detected: 1. Show the changes to user 2. Run `Skill(sync-skills)` to sync ### Step 6: Commit Progress ```bash git add projects//memories// git add projects/*/skills/ # if skill changes git add .claude/skills/ # if skill changes git commit -m "WIP: — " ``` ### Step 7: Summary ``` Session wrapped up: - Memory: - Status: - Next steps captured in notes.md - Committed: ``` ## Tips - Keep notes scannable — bullet points, not paragraphs - Focus on what the next session needs to know to resume - Always commit — don't leave uncommitted wrap-up artifacts

wrap-up-session

Scan your own AI components