careful

To prevent destructive Bash commands, you need guardrails that warn you before execution and require explicit confirmation. This Skill inspects commands via a PreToolUse hook and prompts for confirmation before dangerous actions run.

Yes, requiring confirmation before running commands like rm or git reset is the core function. The guardrails detect destructive patterns in your Bash tools and trigger interactive warnings that prompt you to approve the action.

This safety mode works in production environments by intercepting kubectl delete and similar risky operations. It logs usage analytics and enforces safety checks across both development and production contexts to prevent accidental damage.

You override the Bash guardrails using the per-command override policy. This allows you to bypass the confirmation prompts for specific commands, enabling safe experimentation during development without disabling protection globally.

Yes, python3 is required to use these Bash command guardrails. The environment must have python3 installed to execute the PreToolUse hook that inspects commands and enforces the confirmation workflow.

A limitation of using a PreToolUse hook for destructive command protection is that it only inspects Bash tools for known destructive patterns. Complex or obfuscated commands might bypass the pattern matching if they do not match predefined risk signatures.