careful

Prevent accidental data loss from destructive bash commands by integrating a PreToolUse hook that blocks or warns before executing patterns like rm -rf, DROP TABLE, and git push --force. This provides guardrails against unintended system damage.

Yes, you can configure custom safety settings to allow specific command patterns without triggering a warning. This enables safe execution of approved destructive commands while maintaining protection against unintended data loss.

Command blocking works by integrating as a PreToolUse hook that checks bash commands before execution. It functions within your regular bash workflow to warn or block destructive commands, protecting live systems and shared environments.

The best way to guard shared environments against unintended destruction is enabling command blocking that intercepts destructive commands like git push --force before execution. It requires integration as a PreToolUse hook to check bash commands.

Destructive commands blocked to prevent unintended data loss include rm -rf, DROP TABLE, and git push --force. The command blocking mechanism intercepts these patterns before execution to protect critical systems from accidental damage.