careful

You can prevent destructive bash and git commands by intercepting shell operations via a PreToolUse hook to scan for high-risk patterns like recursive deletes or force-pushes, pausing execution to require explicit user confirmation before proceeding.

Yes, the destructive command checker supports docker, kubectl, and SQL operations by scanning for patterns like docker prune, kubectl delete, and SQL DROP or TRUNCATE statements, requiring an explicit override before executing them in shared environments.

To require confirmation before running kubectl delete or docker prune in production, you apply a pre-execution check that matches these destructive patterns and returns a permission decision requiring explicit user override to proceed.

Yes, you can override the destructive command warning because the pattern detection recognizes common safe cleanups like deleting node_modules or build artifacts, while still allowing manual user override when necessary for other flagged commands.

Yes, you need python3 installed to run this bash command safety checker, as it is a required dependency for executing the pattern matching logic that analyzes your shell and VCS commands before they run.