accidental-data-loss-prevention

Name: accidental-data-loss-prevention
Availability: InStock
Author: SmileAfterBurn

Blocks irreversible deletion commands until explicit user consent is obtained.

Updated Aug 26, 2026

Search Tags:#sql #gcloud #data loss prevention #cloud storage #user consent #destructive commands #safety guardrail

Ready to run

npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill accidental-data-loss-prevention-smileafterburn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accidental-data-loss-prevention
Source: https://github.com/SmileAfterBurn/pani-dumka-ai/tree/main/.gemini/skills/accidental-data-loss-prevention
Command: npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill accidental-data-loss-prevention-smileafterburn

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 in seconds. This Skill acts as a mandatory safety checkpoint that halts any irreversible data-loss operation until the user explicitly approves it. ## Core Features & Use Cases - SQL Protection: Intercepts DROP TABLE/VIEW/SCHEMA/DATABASE, TRUNCATE, and broad DELETE statements missing a WHERE clause or using 1=1. - Cloud Storage & Infrastructure Guardrails: Flags gsutil rm, gcloud storage rm, project deletion, Spanner/BigQuery/Dataproc resource deletion, secret deletion, and KMS key destruction. - Mandatory Consent Workflow: Enforces a three-step procedure of halting execution, explaining the impact and rationale, and waiting for affirmative approval. - Use Case: When asked to clean up a database, the agent pauses before running DROP TABLE on production, explains the impact, and only proceeds after you confirm. ## Quick Start Ask the agent to delete a table or remove a cloud storage bucket and it will stop to request your explicit confirmation before executing anything irreversible.

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 data?▼

Use a consent-gating procedure that halts any irreversible command before execution. The agent explains the deletion impact and rationale, then waits for your explicit affirmative approval before proceeding with operations like DROP TABLE or bucket removal.

What SQL commands are considered destructive?▼

Destructive SQL includes DROP TABLE, DROP VIEW, DROP SCHEMA, DROP DATABASE, TRUNCATE, and broad DELETE statements missing a WHERE clause or using conditions like 1=1. These operations permanently remove data without a recovery path.

Does this cover Google Cloud storage and infrastructure deletion?▼

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

What happens when a destructive command is detected?▼

Execution halts immediately and the command is not run. The agent explains the impact of the deletion and why it may be necessary, then waits for clear affirmative consent from the user before proceeding.

When should I not bypass deletion confirmation prompts?▼

Never bypass confirmation for production data, critical buckets, or shared infrastructure. The safeguard exists because these operations are irreversible, so waiting for confirmation is always preferable to losing critical project assets.