← ClaudeAtlas

git-backuplisted

Full disaster-recovery backup of ~/.claude to a PRIVATE git repo, and non-destructive restore from it. Save triggers on "back up", "git backup", "snapshot my claude config", "DR backup". Restore triggers on "restore from git backup", "recover my claude config".
kai-chop/claude-config-lifeboat · ★ 0 · Code & Development · score 75
Install: claude install-skill kai-chop/claude-config-lifeboat
Extra message: $ARGUMENTS > Requires the kit's scripts installed at `~/.claude/scripts/` (see SETUP.md). The repo > URL lives in `~/.claude`'s git remote (`origin`), not in this file — keep it **private**; > even with the whitelist, your config/memory is yours. ## Pick a mode first - "back up / snapshot / DR backup" -> the **Save** steps below. - "restore / recover" -> jump to the **Restore** section at the bottom. ## Goal Snapshot the whole `~/.claude` (a git work tree whose `origin` is your PRIVATE config repo) for full recovery after a machine failure. Take everything at once — do not cherry-pick; the whitelist `.gitignore` already keeps secrets out. ## Save (one entry point — don't hand-compose add/commit/push) > Why one script: the manual add -> commit -> push -> verify chain kept turning into > hand-composed compound commands, which is exactly where mistakes (and, in Claude Code, > permission-prompt noise) creep in. The unattended SessionEnd hook already runs a > deterministic script — manual saves go through the same single entry. 1. **Run** (pass `$ARGUMENTS` as `-Note` if present; otherwise omit `-Note` entirely): ``` pwsh -NoProfile -File ~/.claude/scripts/auto-backup.ps1 -Note "<$ARGUMENTS>" ``` The script does, in order (do not re-implement these steps by hand — one entry point, one implementation): - snapshots machine config living outside `~/.claude` into `profile/` (your PowerShell profile etc. — extend `$Sources` in `snapshot-machi