- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add waynesutton/builder-skills --skill git-safety -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add waynesutton/builder-skills --skill git-safety -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add waynesutton/builder-skills --skill git-safety -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add waynesutton/builder-skills --skill git-safety -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/waynesutton/builder-skills/tree/HEAD/skills/git-safetyFrom the publisher
These rules exist because one git checkout -- . erased two days of work. Follow them every time, not only when it feels risky.
git status. Read it.git stash push -m "<why>" if the user needs a clean tree and wants the work kept.Never run these on your own. Show the exact command, say what it will destroy, and wait for a yes.
"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.
When the user says "revert that", "undo that", or "go back":
git diff <file> to see exactly what would be lost.Do not reach for git checkout or git restore. They remove everything in the file, including the parts the user liked.
For committed changes, git revert <sha> is safe because it creates a new commit. Still show the sha and the commit message first.
Any time a change is about to be thrown away, the user sees git diff output for it first. No exceptions. If the diff is long, show git diff --stat and offer the full diff.
Do not commit, push, tag, publish, or deploy unless the user asks in the current message. When the work is done, print a suggested commit message and stop.
Suggested commit:
fix: dedupe heartbeat writes within 10s window
These are fine to run without asking:
git status, git log, git diff, git show, git blamegit stash push -m "<message>" when the user asked for a clean treegit add <specific files> when the user asked to commitgit checkout -b <new-branch> from a clean treegit revert <sha> after showing the commitBefore a git command:
git status ran and I read itgit diff for anything being discardedWhen asked to revert or undo:
Stops an agent from destroying uncommitted work with git. Requires git status and git diff before any command that discards changes, treats "revert" and "undo" as manual edits, and never runs reset, c
---name: git-safetydescription: Stops an agent from destroying uncommitted work with git. Requires git status and git diff before any command…---# skills/git-safety/SKILL.mdOverview
Stops an agent from destroying uncommitted work with git. Requires git status and git diff before any command that discards changes, treats "revert" and "undo" as manual edits, and never runs reset, checkout, clean, stash drop, or force push without explicit approval. Use when a task involves reverting, undoing, resetting, cleaning, rebasing, or force pushing, or before any git command in a repo with uncommitted changes.
FAQ
Download skills/git-safety/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/waynesutton/builder-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.