careful

To add a safety prompt before destructive Bash commands, use a PreToolUse hook that detects dangerous patterns like rm -rf or git reset --hard and prompts for confirmation. It logs activity and allows user overrides to proceed when necessary.

Preventing accidental data loss in production environments involves enabling safety guardrails that warn before executing destructive operations. The system detects commands like DROP TABLE or kubectl delete, logs the attempt, and requires explicit user confirmation to proceed.

Yes, you can override the warning prompt for destructive commands. The safety guardrails are customizable and support user overrides, allowing you to bypass the confirmation and proceed with executing the flagged Bash command when necessary.

Yes, the safety guardrail works with specific dangerous commands including git force-push, rm -rf, DROP TABLE, git reset --hard, and kubectl delete. It uses Bash pattern checks to detect these operations and intercept them before execution.

A key limitation of using Bash pattern checks for command safety is that it specifically intercepts Bash commands at execution. It relies on predefined destructive patterns, meaning unrecognized novel destructive operations might not trigger the confirmation prompt.

You need to enable safety mode for shared environment workflows when touching production, debugging live systems, or running potentially destructive Bash commands. This activates the PreToolUse hook to intercept dangerous operations and log usage events for auditing.