recoverlisted

# /recover — Safe recovery from broken git state Walks the operator through a deliberate, **non-destructive** recovery from common failure modes that follow `/dispatch-parallel`, hand-edit mistakes, or interrupted merges. Canonical reference: `docs/playbooks/failure-recovery.md`. **Core principle:** `git reflog` first; destructive operations (`reset --hard`, `clean -fd`, `branch -D`) only after explicit confirmation per step. ## Token budget (MANDATORY) - `git status -s` + `git worktree list` + `git stash list` + `git log --oneline -5` is enough state for 90% of recoveries. Do NOT `git diff` everything up front. - `git reflog | head -30` only when you need to find a lost SHA. - Read FOLLOWUPS.md before writing to it; otherwise no other file reads. - For each recovery branch, the destructive command runs only after the user types literal confirmation ("yes" or the exact SHA). ## Step 1 — Inventory current state Run all four in one shell turn (read-only): ```bash git -C "$PWD" status -s git -C "$PWD" worktree list git -C "$PWD" stash list git -C "$PWD" log --oneline -5 ``` Plus, if the user mentioned a specific branch / SHA / file, also: ```bash git -C "$PWD" reflog | head -30 ``` **Report back** what you see — do NOT act yet. The operator may have context (e.g. "yes that worktree is mine, abandoned") that changes what's safe. ## Step 2 — Classify the failure (user confirms) Match the inventory against one of the named classes. Present the match to the user