- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add waynesutton/builder-skills --skill git-safety -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add waynesutton/builder-skills --skill git-safety -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add waynesutton/builder-skills --skill git-safety -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add waynesutton/builder-skills --skill git-safety -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/waynesutton/builder-skills/tree/HEAD/skills/git-safetyDel publicador
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.mdResumen general
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.
Preguntas frecuentes
Descarga skills/git-safety/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/waynesutton/builder-skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.