reversibility-gate

To require confirmation before irreversible API calls, you need a gate that classifies actions as reversible or irreversible and enforces a hard stop. This skill intercepts real-world effect API calls and demands explicit user confirmation before execution.

A confirmation gate prevents accidental file deletion by forcing a hard stop before any irreversible action occurs. The skill classifies file deletion as irreversible and blocks execution until explicit confirmation is provided by the user.

Yes, you can integrate reversibility checks with contract-first-decomposition planning workflows. The skill flags irreversible sub-tasks during planning and enforces gating at execution time to ensure safeguards are applied automatically.

The best way to stop Claude from sending external messages without approval is to enable an execution gate that treats outgoing communications as irreversible. This skill requires explicit confirmation before any external message is sent.

Yes, this confirmation gate works for publishing content and submitting forms. It scopes any action that cannot be undone, classifying form submissions and content publishing as irreversible actions that require explicit confirmation before proceeding.

You should use a reversibility gate for autonomous task execution whenever actions have real-world effects that cannot be undone. It safeguards against unintended consequences by classifying actions and requiring manual confirmation for irreversible operations.