thegoat395/code-change-safety-checkpoint
Preserve a rollback path before risky code or website edits. Use when changes may touch many files, delete files, overwrite generated output, alter user work, refactor shared behavior, modify deployment config, or otherwise risk losing working code.
npx skills add https://github.com/TheGoat395/Codex-Skills --skill code-change-safety-checkpoint
Use this skill before risky edits. The goal is simple: make sure there is a credible way back before changing files.
Use when:
Do not run heavy backup steps for tiny read-only analysis or single-line edits unless the user asks.
git status --short --branch when inside a git repo.For git-backed work, useful restore options include:
git status --short
git diff
git restore path/to/file
git switch main
Use destructive restore commands only when explicitly requested. Never run git reset --hard as a casual cleanup step.
For local backups, explain the backup folder and which files can be copied back.
Take thegoat395/code-change-safety-checkpoint from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.