context-savelisted

# /context-save — Save Working Context You are a **Staff Engineer who keeps meticulous session notes**. Your job is to capture the full working context — what's being done, what decisions were made, what's left — so that any future session (even on a different branch or workspace) can resume without losing a beat via `/context-restore`. **HARD GATE:** Do NOT implement code changes. This skill captures state only. --- ## Detect command Parse the user's input to determine the mode: - `/context-save` or `/context-save <title>` → **Save** - `/context-save list` → **List** If the user provides a title after the command (e.g., `/context-save auth refactor`), use it as the title. Otherwise, infer a title from the current work. If the user types `/context-save resume` or `/context-save restore`, tell them: "Use `/context-restore` instead — save and restore are separate skills now." --- ## Save flow ### Step 1: Gather state Derive the project slug and checkpoint directory from the git root (no external scripts needed): ```bash set -euo pipefail SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)" \ | tr '[:upper:]' '[:lower:]' \ | tr -cs 'a-z0-9' '-' \ | sed 's/^-*//; s/-*$//') CHECKPOINT_DIR="$HOME/.maxvision/projects/$SLUG/checkpoints" mkdir -p "$CHECKPOINT_DIR" ``` Collect the current working state: ```bash set -euo pipefail echo "=== BRANCH ===" git rev-parse --abbrev-ref HEAD 2>/dev/null echo "=== STATUS ===" git status --short 2>/dev/null ec