accidental-data-loss-prevention

Requires explicit user consent before executing irreversible data deletion commands.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/trungenglish/SHOPWISE --skill accidental-data-loss-prevention-trungenglish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accidental-data-loss-prevention
Source: https://github.com/trungenglish/SHOPWISE/tree/main/.agents/skills/accidental-data-loss-prevention
Command: npx skills add https://github.com/trungenglish/SHOPWISE --skill accidental-data-loss-prevention-trungenglish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Destructive commands like DROP TABLE, TRUNCATE, or gsutil rm can permanently erase production databases, cloud storage buckets, and infrastructure resources in seconds. This Skill prevents accidental data loss by forcing a mandatory verification step before any irreversible deletion runs. ## Core Features & Use Cases - Destructive SQL Guard: Intercepts DROP TABLE/VIEW/SCHEMA/DATABASE, TRUNCATE, and broad DELETE statements missing a WHERE clause or using 1=1. - Cloud Resource Protection: Flags gsutil rm, gcloud storage rm on production buckets, gcloud projects delete, and deletion of Spanner, BigQuery, Dataproc, secrets, or KMS keys. - Mandatory Consent Workflow: Halts execution, explains the impact and rationale, and waits for explicit affirmative user approval before proceeding. - Use Case: When asked to clean up a database, the assistant pauses before running TRUNCATE on a production table, explains the irreversible impact, and only proceeds after you confirm. ## Quick Start Ask the assistant to delete a table or remove cloud storage objects, and it will stop to request your explicit confirmation before running any destructive command.

Frequently Asked Questions about accidental-data-loss-prevention

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent accidental deletion of production database tables?▼

Use a consent-gating procedure that halts any DROP TABLE, TRUNCATE, or broad DELETE statement before execution. The assistant explains the impact and waits for your explicit approval, so destructive SQL never runs without confirmation.

What SQL commands are considered destructive?▼

Destructive SQL includes DROP TABLE, DROP VIEW, DROP SCHEMA, DROP DATABASE, TRUNCATE, and DELETE statements missing a WHERE clause or using a tautology like 1=1. These operations remove data irreversibly and require explicit user consent.

Does this cover Google Cloud storage and resource deletion?▼

Yes, it covers gsutil rm and gcloud storage rm targeting production buckets, gcloud projects delete, and deletion of Spanner, BigQuery, and Dataproc resources. It also guards secrets deletion and KMS key destruction.

What happens when a destructive command is detected?▼

Execution halts immediately and the command is not run. The assistant explains the deletion impact and why it seems necessary, then waits for your clear affirmative consent in the conversation before proceeding.

When should I ask for confirmation before deleting data?▼

Always ask when in doubt, especially for production data or critical project assets. Waiting for confirmation is safer than accidentally deleting data that cannot be recovered.