rotate

Rotation ends this conversation's useful life deliberately: you distill the work into a handoff file and arm it, and the next fresh conversation — most easily one the user starts with `/clear`, without leaving Claude Code — continues from it. This skill writes the handoff and the pending marker. It never ends the conversation and never launches anything. ## Prerequisites Only works in a cs session: check that `$CLAUDE_SESSION_NAME` is set. If empty, tell the user rotation needs a cs session and stop. A rotation needs a purpose — one line describing what the next conversation should do. If the user did not give one, ask before writing anything. ## Process 1. Determine the parent conversation UUID: the `claude_session_id` line of `.cs/local/state`, or if that is missing, `$CS_CLAUDE_SESSION_ID`. Take the state file first. `CS_CLAUDE_SESSION_ID` is the *launch* UUID — cs exports it once per process and never refreshes it, because the SessionStart hook keys its ref-rename guard on that value still naming this process's predecessor. The hook rebinds `claude_session_id` on every fresh conversation, so the two agree only until the first `/clear`. After that the env var names an ancestor, and `parent:` must be the conversation that is writing this handoff — step 7 supersedes by matching it against the session log. 2. Pick a short kebab-case slug from the purpose (e.g. `continue-f5-plan`). 3. Write `.cs/handoffs/YYYY-MM-DD-<slug>.md` (today's date; cre...