backup

Solid

snapshot the history and the working tree, verify that snapshot, then hand back every restore command

Code & Development 1 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

**a snapshot verified, not assumed:** worth typing before anything destructive - worth typing before any reset, rebase, history rewrite or bulk delete - nothing to configure; the destination is fixed and it overwrites nothing - never restores anything; the restore commands are handed back to you # Instructions ## Telemetry ```! "${CLAUDE_PLUGIN_ROOT}"/skills/backup/backup.sh $ARGUMENTS echo "sidecar exit: $?" ``` - `help: requested` → the run was refused before it started; `## Help` below is the whole turn - it already ran, so there is no command to issue - fail (`sidecar exit` > 0) → abort and report: "<raw terminal error>" - a failed snapshot means STOP, never continue into the destructive work it was taken for - success (`sidecar exit` = 0) → continue to step 1 1. report the snapshot, then the restore block, then STOP ```text - /gitgud:backup telemetry data - the snapshot is taken and verified: [backup location] - [git objects copied] objects, [working files copied] working file(s) - [modifications captured] modification(s) and [untracked captured] untracked file(s) ``` - name the location in full, so the user can find it without re-running this trigger - close with the `=== /gitgud:backup handover ===` block as one copy-paste bash block - ignored files are deliberately absent, since `clean -fd` and `reset --hard` never touch them - the snapshot lives inside the repo, so `git clean -fdx` is the one command that eats it -...

Details

Author
MaisonDeVolonte
Repository
MaisonDeVolonte/construct
Created
4 weeks ago
Last Updated
2 days ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category