recovering-from-bad-git-state

Corrupted HEAD occurs when .git/HEAD references a branch that no longer exists. Validate your repository state, identify the corruption type, then reset HEAD to a valid branch reference using targeted recovery procedures that restore consistency between HEAD and branch refs.

Orphaned worktrees are worktree entries that reference deleted directories. Diagnose which worktrees are phantom using validation checks, then prune them safely to remove stale entries and restore repository consistency without affecting active worktrees.

Branch reference inconsistencies occur when HEAD, branch files, and packed-refs fall out of sync. Use state validation to identify corruption type, then apply alignment procedures to reconcile conflicting references and restore a consistent repository state.

Yes. Prevention patterns include integration hooks that validate repository state during common operations, safe worktree management practices, and HEAD consistency checks. Implementing these patterns reduces the likelihood of future corruption.

Run state validation checks to identify corruption type—whether HEAD is broken, worktrees are orphaned, or branch locks conflict. Fast corruption-type identification pinpoints the exact recovery procedure needed, saving time on manual debugging.

Recovery uses standard git operations with validation logic to identify corruption safely. You need git itself and access to your local repository; no external dependencies are required to diagnose and apply targeted recovery procedures.