restorelisted

# /restore — re-hydrate session state from a /checkpoint ## When to run this First command of a new Claude Code session, after the previous session ended with `/checkpoint`. If there's no checkpoint on disk, this skill tells you so and stops — no harm. ## Steps State directory: `$HOME/.claude/.checkpoint/`. ### 0. Auto-update claude-tools (added 2026-05-17) Before rehydrating session state, refresh the toolkit itself so this session uses the latest skills. Look for a cloned `claude-tools` repo at these paths in order: ``` $HOME/claude-tools $HOME/projects/claude-tools $HOME/git/claude-tools $HOME/code/claude-tools /tmp/claude-tools ``` For the first hit (verify with `git remote get-url origin | grep claude-tools`), if the working tree is clean: ```sh cd "$REPO" ./update.sh --quiet -f ``` Behavior: - If already up to date: silent, no output. - If anything changed: show one-line "claude-tools updated: <N> commits, <M> skills" message. Continue with restore. - If `update.sh` exits nonzero: log a one-line warning, continue restore with old version. Don't block rehydration on a network blip. - If working tree is dirty: skip the update with a one-line note ("repo has local changes, skipped auto-update"). The user can manually clean up later. After update succeeds, **note that newly-installed skills are NOT loaded into THIS session** — Claude Code only loads skills at session start. If the update brought in new skill names, the user needs to relaunch Claude Code a