careful

To add a safety prompt before running destructive shell commands like rm -rf, you can use a pre-run hook that scans input commands for risky patterns and returns a permission decision requiring explicit user confirmation before execution.

Yes, you can override the safety warnings for git reset --hard. The precheck mechanism allows explicit user override to proceed after a warning, enabling controlled experimentation and careful production work when you intentionally execute destructive operations.

Yes, this command guardrail approach works for CI/CD pipelines and production environments. The safety hook applies to developer workflows across local machines, CI/CD pipelines, and production touchpoints where destructive operations may be invoked to prevent data loss.

The pre-run hook detects destructive commands during shell and Git actions by scanning for risky patterns such as rm -rf, git reset --hard, kubectl delete, and similar operations to prevent data loss before execution.

To prevent false positives when safety guardrails block benign build artifact deletions, the command scanning mechanism supports safe exemptions for certain build artifacts or benign operations, allowing them to execute without triggering the destructive command warning.

A PreToolUse hook helps prevent data loss in developer workflows by enforcing guardrails directly in tooling, scanning input commands for risky patterns before they execute and requiring an explicit confirmation to proceed with destructive operations.