← ClaudeAtlas

shift-recoverlisted

Rebuilds the state of a session that ended without a handover, after a usage limit, a crash, a closed laptop or a forgotten /clear. Lists the recent sessions for this directory so the user confirms which one, mines its transcript for the last plan, the corrections and what was in flight, checks what actually finished (git state, background and cluster jobs, half-written outputs), then reads back a resume plan and waits before acting. Use when the user says "we hit the limit", "the session died", "continue from yesterday", "I forgot to hand over", "what was I doing", "recover the last session", or when work clearly continues from an earlier session and no handover exists in .shift/.
ruijiezh67/ruijie_skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill ruijiezh67/ruijie_skills
# shift-recover A planned handover is cheap; an unplanned stop is what actually happens. The usage limit hits, the laptop closes, a run eats the context, someone types `/clear`. There is no handover, and the next session starts from nothing while half-finished work sits in the repo and jobs may still be running. This skill reconstructs that state from what survived: the transcript on disk, the repository, and the machines. ## 1. Pick the session, by name not by id Run `python "${CLAUDE_SKILL_DIR}/../shift-change/scripts/mine_transcript.py" --list` (or the same script inside the shift-change skill directory) to list recent sessions for this directory: id, time span, number of prompts, opening line. Show the user that list in a readable form and let them confirm with a word ("yesterday's", "the sweep one"). If only one plausible session exists, name it and continue. If no transcript survives (Claude Code deletes old sessions, around 30 days by default), say so plainly and rebuild from the repository alone; everything below except step 2 still applies. ## 2. Mine the transcript Run the same script with `--session <id>`. It prints the user's messages (corrections flagged, pre-compaction ones labelled), rejected tool calls and interruptions, files edited and read, and the commands that may still be running. Read it for four things: - **The last intent**: what the user asked for most recently, and what the agent was in the middle of doing. - **Corrections and preferences**,