Skip to content
Back to skills

Ask Before Irreversible

ASecurity

Sort every action into reversible or not, and pause for an explicit yes before anything that deletes data, rewrites shared history, deploys, spends money or reaches other people.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 22, 2026
ai-agentsgogitdatabase

Security analysis

A100/100

Scanned October 22, 2026

npx -y skills add gaurav8936/oneroof --skill ask-before-irreversible --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ask Before Irreversible?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ask Before Irreversible
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gaurav8936-ask-before-irreversible/badge)](https://www.skillsdirectory.com/skills/gaurav8936-ask-before-irreversible)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ask-before-irreversible
description: Sort every action into reversible or not, and pause for an explicit yes before anything that deletes data, rewrites shared history, deploys, spends money or reaches other people.
runtime: [shared]
triggers: [is this safe, before I delete, approval, confirm first]
---

# ask-before-irreversible — pause where undo is hard

## Two kinds of action

| Go ahead | Stop and ask first |
|---|---|
| Edit files, run tests, local commits | Delete files or branches you did not create |
| Create a branch or worktree | `git push --force`, `reset --hard` on a shared branch, rewriting history |
| Read logs, query read-only | Write to a production database, run migrations |
| Draft a message | Send email, Slack, issues or comments to other people |
| Build locally | Deploy, publish, release, change DNS or permissions |
| | Anything that spends money or changes billing |

## How to ask

One short message: **what** you want to do, **why**, **what it affects**, and **how to undo it** (or "cannot be
undone"). Then wait. A yes covers that action only; the next risky action gets its own question.

## Before deleting or overwriting

Look at the target first: list it, read it, check `git status`, and check whether anyone else (another session, a
teammate) has work there. If something unexpected is there, stop and report it rather than clear it.

## Never

- Never treat an earlier yes as permission for a different or bigger action.
- Never work around a block (a hook, a permission denial, a failing gate) by finding another route. Report it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.