---
name: git-safety
description: 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.
title: git-safety
canonical_url: https://skilld.dev/gh/waynesutton/builder-skills/git-safety
last_updated: 2026-09-29T15:01:40.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/git-safety/agents/openai.yaml), [assets/large-logo.png](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/git-safety/assets/large-logo.png), [assets/small-logo.svg](https://skilld.dev/api/skills-raw/waynesutton/builder-skills/git-safety/assets/small-logo.svg).
>
> If the user asked to install this Skill, run `npx skilld install waynesutton/builder-skills/git-safety`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/git-safety`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/waynesutton/builder-skills/git-safety) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/git-safety`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/git-safety --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/git-safety --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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 would be lost.
3. Read the current file.
4. Edit the file by hand to remove the specific lines that are wrong. Keep everything else.
5. Show the result.

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.

## Diff before discard

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.

## Commits, pushes, deploys

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
```

## Safe defaults

These are fine to run without asking:

- `git status`, `git log`, `git diff`, `git show`, `git blame`
- `git stash push -m "<message>"` when the user asked for a clean tree
- `git add <specific files>` when the user asked to commit
- `git checkout -b <new-branch>` from a clean tree
- `git revert <sha>` after showing the commit

## Checklist

Before a git command:

- [ ] `git status` ran and I read it
- [ ] no uncommitted work is in the blast radius, or the user approved
- [ ] I showed `git diff` for anything being discarded
- [ ] the command is not in the approval table, or the user said yes to this exact command

When asked to revert or undo:

- [ ] I know which change and whether it is committed
- [ ] I am editing the file, not checking it out
- [ ] everything the user did not mention stays
