careful

You can prevent accidental destructive commands by using a bash-based prehook that analyzes risky operations like rm -rf or git reset --hard and requires explicit confirmation before executing them.

Yes, you can override warnings for destructive actions when necessary, enabling controlled risk-taking in critical contexts like debugging live systems or touching production environments.

Yes, the safety guardrail works in development, staging, and production environments, preventing data loss or downtime by warning users before executing risky commands.

The PreToolUse hook analyzes destructive operations such as rm -rf, git push --force, git reset --hard, kubectl delete, and similar risky commands before execution to prevent accidental data loss.

The bash prehook logs usage analytics locally, recording incidents when users attempt risky commands and requiring explicit confirmation or override before proceeding with execution.

The best way to add safeguards against force-push and kubectl delete is implementing a bash-based hook that warns users before executing these destructive actions and logs the incidents locally.