careful

You can get warning prompts before destructive bash commands by enabling a PreToolUse hook that scans commands like rm -rf or git reset --hard, asks for confirmation, and logs usage while allowing overrides to proceed when necessary.

Destructive commands that should trigger safety guardrails include rm -rf, DROP TABLE, git reset --hard, kubectl delete, and docker prune. A PreToolUse hook scans for these operations and prompts for confirmation before allowing execution in Bash environments.

Yes, you can override the confirmation prompt for destructive commands in production. The safety guardrail provides override options to proceed when necessary, ensuring essential work continues while maintaining visible audit prompts and logging usage.

To prevent accidental data loss from rm -rf or DROP TABLE in shared environments, implement a PreToolUse hook that proactively scans commands and prompts for confirmation before execution. This provides guardrails for operators, developers, and SREs without blocking essential workflows.

No, this bash safety hook does not block destructive commands completely. It implements a proactive prompt that warns before execution and provides override options, allowing you to cancel or proceed with commands like kubectl delete or docker prune while logging usage.

The best way to add guardrails for destructive commands without blocking essential work is implementing a PreToolUse hook that scans commands, prompts for confirmation, and logs usage. This provides safety warnings for development, production maintenance, and shared systems while allowing necessary overrides.