Coding Worktree Recovery

Use this skill when coding-agent work is interrupted, an agent exits without a clean commit, multiple controllers target the same checkout, or the checkout produces inconsistent file/Git behavior.

This skill is about preserving valid work and restoring one trustworthy writer. It does not authorize pushing, merging, publishing, or destructive cleanup.

Core invariants

1. One checkout, one writer. Read-only reviewers may overlap; write-capable agents may not.
2. The live filesystem is authoritative. Agent summaries and successful process exits are evidence leads, not proof.
3. Never clean another writer's work. Do not reset, stash, checkout, delete, or overwrite unexplained changes.
4. Commits are checkpoints, not completion. Re-run controller gates after the final commit.
5. Mechanical status and reasoning are separate. A deterministic watchdog may report process/Git state; acceptance still requires a controller review.

Recovery workflow

1. Freeze new writers