backup
Solidsnapshot the history and the working tree, verify that snapshot, then hand back every restore command
Install
Quality Score: 82/100
Skill Content
Details
- Author
- MaisonDeVolonte
- Repository
- MaisonDeVolonte/construct
- Created
- 1 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
git-backup
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".
backup
Give a project on the shared VPS a nightly off-box backup, or work on one it already has — provision its Backblaze bucket and bucket-scoped key, write its script and systemd units, render its credentials, and prove the restore by running it rather than describing it. Encodes the toolkit these co-tenants share: restic to B2, one bucket per project, credentials in /etc/<tenant>/backup.env, a staggered timer, and a drill. TRIGGER when: a project needs a backup it does not have; an existing backup needs changing, diagnosing, or restoring from; a nightly backup unit has failed; a restic repository or a Backblaze bucket/key must be created; or someone asks where a project's snapshots live. DO NOT TRIGGER when: the task is a one-off dump taken by hand for a migration or a schema change, a git or source-code backup, or a project that is not a tenant of this box.
nuke
price what a hard reset would take, take the backup that makes it survivable, then hand back the rest