Git Safety Net

What it does

• Recover (Mode A): walks the git reflog → git fsck --dangling ladder to bring back "deleted" commits, branches and stashes (usually still in the object store for ~90 days), always onto a fresh rescue/... branch instead of resetting live work.
• Audit & preserve (Mode B): finds every checkout of the repo on the machine — including independent git clones that git worktree list, git branch -a and git fsck are structurally blind to — then reports unpushed commits, dirty worktrees, stashes and dangling commits per checkout. At-risk objects get pinned under refs/dangling-backup/, exported as patches/bundles, and untracked files get plain-copied (bundle/archive can never reach them).
• Verify merged (Mode C): never trusts commit counts (squash merges create hundreds of phantom "ahead" commits). It runs an in-memory trial merge with git merge-tree and only reports MERGED when the merge changes nothing.
• Prevent (Mode D): commit-then-switch instead of stash or a second clone; git branch -f instead of reset --hard in a shared tree; plumbing-only commits when another session holds the worktree.
• Retire safely (Mode E): a supersession triage ladder (git cherry → superset diff → symbol probe) plus backup-gated deletion order for stashes, worktrees, branches and clones.

Who it's for

• Developers who just rebased or force-pushed and fear work vanished
• Anyone sitting on dozens of stale branches, stashes and worktrees, unsure what's safe to delete
• Teams or multiple AI agents working in parallel on one shared repository
• Leads who need defensible proof that "everything is merged" before a release or cleanup

Examples

1. "I lost yesterday's commit" → locate the SHA in the top of the reflog, confirm with git show, recover onto rescue/lost-feature.
2. "Can I delete this clone directory?" → git_find_all_checkouts.sh surfaces a sibling clone holding 440 lines of untracked work; back it up first, then delete behind a backup-exists guard.
3. "Clean up 30 old branches and keep only main" → run git_verify_branch_merged.sh per branch, delete only those reported MERGED (content contained), keep anything unproven.

Install the skill I found on Claude Skill Mart.
Copy the git-safety-net folder from the GitHub repo daymade/claude-code-skills into my ~/.claude/skills/git-safety-net/.
When it's done, tell me in one line what this skill can do.