git-safetylisted
Install: claude install-skill waynesutton/builder-skills
# Git safety
These rules exist because one `git checkout -- .` erased two days of work. Follow them every time, not only when it feels risky.
## Before any git command
1. `git status`. Read it.
2. If anything is modified or untracked, stop. Say what is there. Ask before proceeding with anything that could touch those files.
3. Suggest `git stash push -m "<why>"` if the user needs a clean tree and wants the work kept.
## Commands that need explicit approval
Never run these on your own. Show the exact command, say what it will destroy, and wait for a yes.
| Command | What it destroys |
| --- | --- |
| `git reset --hard` | every uncommitted change |
| `git checkout -- <file>` or `git restore <file>` | uncommitted changes in that file |
| `git checkout -- .` or `git restore .` | uncommitted changes in every file |
| `git clean -fd` | every untracked file and folder |
| `git stash drop` or `git stash clear` | stashed work |
| `git push --force` or `--force-with-lease` | remote history other people may have |
| `git branch -D` | a branch and any commits only it holds |
| `git rebase` on a shared branch | commit ids other people have |
"Explicit approval" means the user saw the command and said yes to it. A general "go ahead" from earlier in the conversation does not count.
## Revert and undo mean edit
When the user says "revert that", "undo that", or "go back":
1. Ask which change. Committed or uncommitted? All of it or one part?
2. `git diff <file>` to see exactly what w