Localsetup localsetup-unfuck-my-git-state
Diagnose and recover broken Git state and worktree metadata with a staged, low-risk recovery flow. Use when Git reports detached or contradictory HEAD state, phantom worktree locks, orphaned worktree entries, missing refs, 0000000000000000000000000000000000000000 hashes, or branch operations fail with errors like already checked out, unknown revision, not a valid object name, or cannot lock ref.
git clone https://github.com/CruxExperts/localsetup
T=$(mktemp -d) && git clone --depth=1 https://github.com/CruxExperts/localsetup "$T" && mkdir -p ~/.claude/skills && cp -r "$T/_localsetup/skills/localsetup-unfuck-my-git-state" ~/.claude/skills/cruxexperts-localsetup-localsetup-unfuck-my-git-state && rm -rf "$T"
_localsetup/skills/localsetup-unfuck-my-git-state/SKILL.mdunfuck-my-git-state
Recover a repo without making the blast radius worse.
Core Rules
- Snapshot first. Do not "just try stuff."
- Prefer non-destructive fixes before force operations.
- Treat
as production data until backup is taken..git/ - Use
before manually editinggit symbolic-ref
..git/HEAD - After each fix, run verification before proceeding.
Fast Workflow
- Capture diagnostics:
python scripts/snapshot_git_state.py .
- Route by symptom using
.references/symptom-map.md - Generate non-destructive command plan:
python scripts/guided_repair_plan.py --repo .
- Apply the smallest matching playbook.
- Run
verification gate.references/recovery-checklist.md - Escalate only if the gate fails.
For explicit routing:
python scripts/guided_repair_plan.py --list python scripts/guided_repair_plan.py --symptom phantom-branch-lock
Regression Harness
Use disposable simulation tests before changing script logic:
python scripts/regression_harness.py
Run one scenario:
python scripts/regression_harness.py --scenario orphaned-worktree
Playbook A: Orphaned Worktree Metadata
Symptoms:
shows a path that no longer exists.git worktree list- Worktree entries include invalid or zero hashes.
Steps:
git worktree list --porcelain git worktree prune -v git worktree list --porcelain
If stale entries remain, back up
.git/ and remove the specific stale folder under .git/worktrees/<name>, then rerun prune.
Playbook B: Phantom Branch Lock
Symptoms:
orgit branch -d
fails with "already used by worktree".git branch -D
seems to disagree with branch ownership.git worktree list
Steps:
git worktree list --porcelain
Find the worktree using that branch, switch that worktree to another branch or detach HEAD there, then retry the branch operation in the main repo.
Playbook C: Detached or Contradictory HEAD
Symptoms:
says detached HEAD unexpectedly.git status
andgit branch --show-current
disagree.git symbolic-ref -q HEAD
Steps:
git symbolic-ref -q HEAD || true git reflog --date=iso -n 20 git switch <known-good-branch>
If branch context is unknown, create a rescue branch from current commit:
git switch -c rescue/$(date +%Y%m%d-%H%M%S)
Then reconnect to the intended branch after investigation.
Playbook D: Missing or Broken Refs
Symptoms:
,unknown revision
, ornot a valid object name
.cannot lock ref
Steps:
git fetch --all --prune git show-ref --verify refs/remotes/origin/<branch> git branch -f <branch> origin/<branch> git switch <branch>
Use
reflog to recover local-only commits before forcing branch pointers.
Last Resort: Manual HEAD Repair
Only after backup of
.git/.
Preferred:
git show-ref --verify refs/heads/<branch> git symbolic-ref HEAD refs/heads/<branch>
Fallback when
symbolic-ref cannot be used:
echo "ref: refs/heads/<branch>" > .git/HEAD
Immediately run the verification gate.
Verification Gate (Must Pass)
Run checks in
references/recovery-checklist.md. Minimum bar:
exits cleanly with no fatal errors.git status
matches intended branch.git symbolic-ref -q HEAD
has no missing paths and no zero hashes.git worktree list --porcelain
has no new critical errors.git fsck --no-reflogs --full
Escalation Path
- Archive
:.git
tar -czf git-metadata-backup-$(date +%Y%m%d-%H%M%S).tar.gz .git
- Clone fresh from remote.
- Recover unpushed work with reflog and cherry-pick from old clone.
- Document failure mode and add guardrails to automation.
Automation Hooks
When building worktree tooling (iMi, scripts, bots), enforce:
- preflight snapshot and state validation
- post-operation verification gate
- hard stop on HEAD/ref inconsistency
- explicit user confirmation before destructive commands
Resources
- Symptom router:
references/symptom-map.md - Verification checklist:
references/recovery-checklist.md - Diagnostic snapshot script:
scripts/snapshot_git_state.py - Guided plan generator:
scripts/guided_repair_plan.py - Disposable regression harness:
scripts/regression_harness.py