agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/code-change-safety-checkpoint/SKILL.md

code-change-safety-checkpoint

Skill136 starsChanged 5 months agoMITView on GitHub

Preserve rollback before materially risky edits.

  • Deletes or force-pushes

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill before risky edits.

    line 8
  2. Distinctive:

    Do not run heavy backup steps for tiny read-only analysis or single-line edits unless the user asks.

    line 20
  3. Distinctive:

    Run git status --short --branch when inside a git repo.

    line 25
  4. Distinctive:

    Treat uncommitted user changes as protected.

    line 27
  5. Distinctive:

    Follow the current repository/worktree branch policy.

    line 30
  6. Distinctive:

    If the repo has user changes, preserve the affected hunks and untracked targets with an appropriate patch, snapshot or scoped backup when …

    line 31
  7. Distinctive:

    If there is no git repo or the work involves generated assets, make a timestamped local backup of the files or folders you will touch.

    line 32
  8. Distinctive:

    Call out any deletion, move, or overwrite.

    line 36
  9. Distinctive:

    Do not revert user changes unless explicitly requested.

    line 41
  10. Distinctive:

    Prefer additive changes when the risk is unclear.

    line 42
  11. Distinctive:

    Use destructive restore commands only when explicitly requested.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Trigger

Use when:

  • the user asks for website, app, repo, or code changes with nontrivial blast radius
  • files may be deleted, moved, regenerated, overwritten, or mass-edited
  • the repo has uncommitted changes
  • the work touches shared behavior, routing, deployment config, generated assets, or build tooling
  • the user specifically asks for backup, checkpoint, rollback protection, or protection from accidental destructive changes

Do not run heavy backup steps for tiny read-only analysis or single-line edits unless the user asks.

Workflow

  1. Inspect state before editing.
    • Run git status --short --branch when inside a git repo.
    • Identify changed files that already exist before your work.
    • Treat uncommitted user changes as protected.
  2. Choose the rollback path.
    • Follow the current repository/worktree branch policy. Record a recoverable base commit for tracked data; a branch label alone does not preserve uncommitted or untracked files.
    • If the repo has user changes, preserve the affected hunks and untracked targets with an appropriate patch, snapshot or scoped backup when the edit could destroy them. Avoid redundant copies of already protected targets.
    • If there is no git repo or the work involves generated assets, make a timestamped local backup of the files or folders you will touch.
  3. Explain planned edits before changing files.
    • List the main files or directories you expect to edit.
    • Call out any deletion, move, or overwrite.
    • A clear task instruction authorizes routine in-scope edits regardless of its verbs. Ask only for a materially ambiguous destructive target or another genuinely missing authorization.
  4. Edit narrowly.
    • Avoid unrelated refactors.
    • Do not revert user changes unless explicitly requested.
    • Prefer additive changes when the risk is unclear.
  5. Report the restore path.
    • Branch name, backup path, or commit/checkpoint strategy.
    • Commands or steps needed to undo your work.

Restore Guidance

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.