careful

To add safety guardrails for destructive bash commands, you need a warning system that intercepts dangerous operations like rm -rf before execution. This Skill implements a PreToolUse hook that detects risky commands and requires explicit override to proceed.

Yes, you can override the warning for destructive commands in prod mode using per-command override options. This allows trusted operations to proceed after the initial guardrail warning is triggered, ensuring intentional execution of necessary destructive actions.

Yes, this safety hook works with kubectl delete and git reset --hard. It applies to Bash-based workflows and covers a wide range of destructive operations across local machines, servers, and CI pipelines by issuing real-time warnings.

The best way to prevent accidental destructive actions in CI pipelines is using a PreToolUse hook with YAML frontmatter configuration. It monitors Bash-based workflows across shared environments and provides real-time warnings before dangerous commands execute.

You configure warning behavior for specific bash commands using YAML frontmatter. This configuration supports per-command override behavior, allowing you to define exactly which destructive operations require warnings and how to handle explicit overrides.

You should use a bash command guardrail during prod maintenance, debugging in shared environments, or any scenario requiring careful command execution. It prevents accidental destructive actions by warning before dangerous commands are executed across machines and servers.