careful

To prevent destructive shell commands like rm -rf, you need safety guardrails that enforce pre-run checks and require explicit confirmation before execution. This intercepts dangerous commands via a PreToolUse hook to stop data loss.

Yes, you can add safe exceptions for common build artifacts and test data. This allows specific non-critical files to bypass the destructive command warnings while still protecting essential system data.

Yes, the shell safety guardrail works with git reset --hard and kubectl delete. It detects these specific destructive commands, prompts a warning, and requires explicit confirmation before allowing them to proceed.

The best way to add a pre-hook for destructive commands in bash is to enforce pre-run checks using a PreToolUse hook. This mechanism prompts explicit confirmation and logs usage locally for auditing.

You need to confirm destructive commands during production debugging because commands like docker prune could cause irreversible data loss. Safety guardrails ensure you explicitly approve these actions before execution.

Yes, you can override the warning to proceed when necessary. The safety guardrails prompt you with a warning and require explicit confirmation, allowing you to bypass the block if you intentionally need to run the command.