careful

You can add safety warnings for destructive bash commands by implementing a PreToolUse hook that runs a safety script. This intercepts risky operations like rm -rf or git reset --hard, warning you before execution across interactive shells and automated workflows.

Yes, you can override warnings on a per-command basis. The guardrail prompts you with explicit confirmation before executing destructive commands, allowing you to bypass the safety check intentionally when pushing to prod or deleting resources.

Yes, the bash guardrail works across automated workflows and shared environments. It prevents data loss by intercepting destructive operations in CI scripts and interactive shells, logging usage analytics to track when overrides occur during debugging.

The safety guardrail catches destructive bash commands including rm -rf, DROP TABLE, force-push, git reset --hard, and kubectl delete. It warns you before these risky operations execute to prevent data loss in production and development environments.

You should use a bash guardrail when touching production, debugging live systems, or working in a shared environment. It provides pre-execution warnings for dangerous commands, preventing accidental data loss during sensitive maintenance tasks.