careful

To prevent accidental damage from destructive commands, you need safety guardrails that warn before execution. This Skill intercepts shell and deployment operations like rm -rf and git reset --hard, prompting for confirmation before proceeding.

Yes, you can override destructive command warnings for authorized actions. The Skill provides an explicit override option, allowing you to proceed with necessary destructive operations while still logging the event for auditing.

Yes, this safety guardrail works with database and Kubernetes operations. It detects destructive patterns like DROP statements and kubectl delete commands across services, returning a warning to prevent accidental data loss in production environments.

Shell safety guardrails analyze commands using a PreToolUse hook that inspects the incoming command pattern. If a destructive operation is detected, it returns a permission decision requesting user confirmation before the command executes.

The best way to audit destructive command usage is by logging override events locally. This Skill records usage analytics for guardrail events, providing an audit trail to reduce risk during collaborative debugging and live-system work.

A limitation of using the command override option is that authorized destructive actions will still execute after the warning. While the guardrail logs the event for auditing, it cannot reverse operations like git push --force once the override is applied.