← ClaudeAtlas

save-contextlisted

Saves what a working session decided, changed, learned or left open, so the next conversation starts with it already in context. Discovers what the project keeps (STATUS.md, CLAUDE.md, the agent's memory files, registers, context folders), maps each item from the conversation to the one place it belongs, shows the user the plan in one list, writes it after approval (or straight away when the config turns approval off), hands items to other skills that own a destination, and commits only the files it touched without pushing. Works in any project. Use at the end of a session, or as a checkpoint before switching to a different task. Triggers on "save context", "save-context", "wrap up", "wrap-up", "close the session", "did you update everything", "update status and memory", "save the context", "before we close", "before I close this", "handoff", "checkpoint", "make sure the next session knows".
mutlumehmet/claude-plugins · ★ 6 · AI & Automation · score 76
Install: claude install-skill mutlumehmet/claude-plugins
# Save context before closing a session The goal is one thing: **a fresh session, reading only what the project already tells it to read, must know everything from this conversation that matters later.** Anything that only mattered inside this conversation stays out. Pre-approved tools are kept narrow on purpose: reading, edits to STATUS.md, CLAUDE.md and the memory folder, and the read and commit git commands. Anything else (a register, another skill, a push) asks the user first, which is the intended behaviour, not an error. ## Step 0: Load the config (optional) The config lives at `$SAVE_CONTEXT_CONFIG` if set, otherwise `~/.config/save-context/config.yaml`. Read that file with the Read tool if it exists (expand `~` to the home folder). Every key is optional and the skill works with no file at all, so there is no setup round. If the file is missing, use the defaults below and carry on. `config.example.yaml` next to this file documents each key. | Key | Default | Effect | |---|---|---| | `tasks_skill` | empty | Skill that records dated promises and to-dos (for example a Notion or Todoist task skill). Empty: such items go to STATUS.md under next steps | | `commit` | `true` | Commit the touched files at the end. `false`: leave them uncommitted and say so. Pushing never happens either way | | `confirm` | `true` | Show the plan and wait for approval (Step 4). `false`: write everything straight away with no question, for users who say "save context" and walk away from the