careful

To add a warning prompt before destructive bash commands, implement pattern-based checks that detect rm -rf and prompt for confirmation before execution. This guardrail applies in interactive shells and automated scripts to prevent accidental data loss.

Yes, you can safely override a guardrail warning to proceed with a git reset --hard. The override mechanism allows you to bypass the confirmation prompt after acknowledging the risk of the destructive command.

Yes, this command safety check works with kubectl delete operations in automated scripts. It provides a JSON-based permission response that integrates with automated frameworks to warn and require confirmation for dangerous actions.

You can configure a safe-exceptions list to whitelist specific destructive commands by defining approved patterns. Commands matching these exceptions bypass the warning and confirmation prompts, allowing execution without triggering the guardrail.

You need a destructive command guardrail in production debugging contexts when actions like rm -rf, git reset --hard, or kubectl delete risk irreversible data loss in shared environments. The guardrail ensures you confirm before executing dangerous operations.