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.

This skill appears coherent and repository-scoped, but review and run it consciously: 1) Inspect the scripts locally before executing. 2) Run the regression harness in a disposable environment first if you want to validate behavior. 3) The tool creates snapshots under the repo (./.git-state-snapshots) and may instruct you to create tar backups — make sure you have disk space and that storing such backups in the current directory is acceptable. 4) Follow the recommended verification gate and backup steps before performing any of the 'last resort' commands (editing .git/HEAD, force-moving branches, or removing .git/worktrees). 5) Because this skill executes Bash scripts against your repo, avoid running it as a privileged user or against a repo containing sensitive unpushed data unless you have backups.

Type: OpenClaw Skill Name: unfuck-my-git-state Version: 0.2.1 The skill bundle aims to diagnose and recover corrupted Git repository states. While it involves commands that can modify Git state, including direct manipulation of `.git/HEAD` (e.g., in `SKILL.md` and `references/symptom-map.md`), these are explicitly presented as 'last resort' or 'escalation' steps, always preceded by strong recommendations to 'Snapshot first' and 'back up .git/'. All scripts are local, perform read-only diagnostics or controlled modifications within the repository, and do not exhibit any signs of data exfiltration, malicious execution, persistence, obfuscation, or prompt injection with harmful intent. The `regression_harness.sh` script safely simulates these scenarios in temporary directories for testing purposes.