careful

Preventing accidental data loss from destructive bash commands like rm -rf requires safety guardrails that scan command inputs for high-risk patterns and prompt you for confirmation before execution. This mechanism intercepts recursive file deletions to protect critical production systems.

You can block git push --force and git reset --hard by applying a safety skill that detects destructive git operations and requires manual confirmation. This prevents accidental execution of commands that would permanently rewrite shared repository history and disrupt team workflows.

Yes, destructive command detection includes safe exception handling that automatically allows common build artifact deletions like node_modules, dist, and __pycache__ without triggering warnings. This ensures workflow efficiency while maintaining protection against actual data loss from high-risk patterns.

Yes, you can get confirmation prompts before running kubectl delete or docker system prune by activating safety guardrails for Kubernetes and Docker operations. The detection system scans these specific high-risk commands and halts execution until you manually confirm the destructive action.

The best way to prevent accidental SQL data drops in production databases is to implement a command scanning safety layer that detects DROP TABLE queries and prompts for explicit confirmation. This adds a critical verification step before any permanent database schema or data deletion occurs.

You should use destructive command safety guardrails in DevOps workflows when working in shared environments or critical production systems. They are essential whenever executing bash commands, git operations, or database queries where accidental data loss or system disruption could cause permanent damage.