← ClaudeAtlas

irreversible-gatelisted

Use this protocol before executing any action that cannot be cheaply undone: pushing to a shared branch, deploying, running a database migration, deleting data or resources, sending an email or message, spending money or calling a paid API in bulk, publishing anything public, or rotating or revoking secrets. Load BEFORE the action, not after.
SeamStressDev/seam-scaffold · ★ 0 · AI & Automation · score 72
Install: claude install-skill SeamStressDev/seam-scaffold
# Irreversible Gate ## What this is Most mistakes in a coding session cost an undo. A small number cost a customer, a database, or a reputation. This gate exists for the second kind. It adds friction to exactly one class of action and leaves everything else alone. The gate is a set of questions the human answers before the action runs. The questions are short. The point is not the ceremony. The point is that irreversible mistakes are almost always visible one minute before they happen, to anyone who actually looks. ## Trigger Before executing any action in the irreversible class: - **Push** to any default branch, or to any branch another person or system is known to consume (a teammate's checkout, a CI trigger, a deploy hook). Local commits are reversible; push is the line. Unsure whether anyone consumes the branch: gated. - **Deploy** to any environment reachable by anyone outside this session, including staging with internal testers. An environment is "internal only" if no one but you can reach it; three beta users are users. - **Migrate** a database schema, or run any bulk write against real data - **Delete** data, files outside the working tree, branches on a remote, or cloud resources - **Send** an email, message, or notification to a real person - **Spend** money, or start a bulk run against a paid API - **Publish** anything public: a package, a release, a post, a PR to someone else's repo - **Rotate or revoke** secrets, keys, or access If an action is no