Destructive ops approval
Skill 26zl/universal-agent-skills/skills/destructive-ops-approval
Canonical Agent Skills with idempotent cross-agent installers for Claude Code, Codex, OpenCode, and GitHub Copilot
npx -y skills add 26zl/universal-agent-skills --skill destructive-ops-approvalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Obtain explicit confirmation before irreversible or outward-facing operations such as force-pushes, history rewrites, mass deletion, data migrations, or production changes, and prefer the reversible alternative when one exists. Use when an action could destroy data, rewrite shared history, or change systems other people depend on; do not use to stall routine, easily reversible work.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, as published. Nobody here has run it
Destructive Ops Approval
Irreversible actions get a human decision first, every time.
Rules
- Before force-pushing, rewriting shared history, deleting branches or tags others may use, mass-deleting files or records, dropping schemas, or changing production configuration, state the action, the blast radius, and the rollback plan, then wait for explicit approval.
- Approval covers one action in one context; it does not carry over to the next occasion or a wider scope.
- Prefer the reversible form when one exists: soft deletes, archives, expiring backups, feature flags, force-with-lease over force, dry run before apply.
- Take a verified backup or snapshot before an approved destructive step, and confirm the restore path works.
- Scope credentials and commands to the narrowest target that completes the task; never widen a destructive command to save a step.
- If the target's state does not match what the approval assumed, stop and re-confirm instead of proceeding.
Boundaries
- Routine local, reversible operations need no ceremony.
- Organizational emergency procedures override this skill's pacing; follow them exactly.