careful

To prevent destructive Bash commands, you need a PreToolUse hook that scans input for risky patterns like rm -rf and warns before execution. This skill intercepts commands across local, staging, and production environments, allowing you to cancel or accept the risk.

Yes, you can get a warning before running git reset --hard or git push --force by using a Bash command scanner. It detects these specific risky patterns and prompts you with an override or cancel option to preserve system safety.

Yes, this safety guardrail works with Kubernetes and Docker cleanup commands by detecting operations like kubectl delete and docker system prune. It scans these Bash-driven inputs and allows you to override the warning or cancel the action entirely.

You can override a destructive command warning by choosing to proceed when prompted. The user-driven override feature allows you to accept the risk and execute the Bash command, or cancel it to maintain production safety guardrails.

A limitation of using Bash hooks to block destructive commands is that they rely on pattern matching for known risks like git push --force. Users must manually evaluate and accept risks during overrides, and configure optional exemptions for specific workflows.