careful

You can prevent destructive bash commands by using a pre-execution check hook that identifies operations like rm -rf in real time and prompts for confirmation before execution. This safety guardrail intercepts the command before it runs.

Yes, you can override the safety warning when you intentionally need to run git reset --hard. The guardrail prompts for explicit confirmation, allowing you to bypass the block and preserve your workflow when the destructive action is truly intended.

Yes, this destructive command guardrail works for kubectl delete operations in production. It acts as a safety layer applicable in development, production touchpoints, and shared environments where destructive actions may occur.

A pre-execution check hook for bash is a safety mechanism that scans commands before they run. It stops force-push by identifying the destructive operation in real time, warning you, and requiring explicit confirmation or override to proceed.

You enable safety mode for debugging live systems by activating the shell session guardrail. This implements a PreToolUse Bash hook that signals warnings before destructive operations, prompting you to confirm each action to proceed only when truly intended.

The bash guardrail warns about DROP TABLE commands by scanning shell input, but its scope is limited to bash commands. It provides audit-ready logging and override capabilities, though it does not block execution if you explicitly confirm the destructive action.