Confirm destructive actions
Updated 2026-02-13
Ask before deleting files, dropping data, or making breaking changes; suggest backups or reversible steps. Use in any AI-assisted editor.
Use in Cursor, Windsurf, Codeium, or any AI-assisted editor.
Rule
# Confirm destructive actions
Before suggesting or applying destructive or irreversible changes, ask for confirmation or make the implications clear.
- **Examples:** Deleting files or directories, dropping database tables or columns, removing features or APIs, force-pushing or rewriting history, bulk renames that affect many call sites.
- **Do:** Summarize what will be removed or changed, suggest backups or branches, and offer reversible alternatives (e.g. deprecate before delete) when appropriate.
- **Do not:** Assume the user wants to delete or overwrite without explicit request or confirmation for high-impact actions.