careful

Preventing destructive bash commands in production requires a pre-execution hook that scans input for risky patterns like rm -rf or git reset --hard and prompts for explicit confirmation before execution. This intercepts dangerous operations before they cause accidental data loss.

Destructive shell commands include patterns such as rm -rf, git reset --hard, and SQL DROP or TRUNCATE statements. A safety hook identifies these risky operations during pre-execution scanning and blocks them unless explicit user confirmation is granted.

Yes, non-destructive build artifacts can be safely ignored through safe-exceptions during command safety checks. This allows routine build and deployment tasks to proceed without interruption while still intercepting genuinely destructive patterns.

This command safety hook works during database maintenance, system administration, and deployment by inspecting shell input before execution. It flags risky SQL patterns like DROP and TRUNCATE, requiring confirmation to prevent accidental data loss in shared environments.

The best way to add a confirmation prompt for risky shell operations is implementing a hook-based pre-execution check that flags dangerous patterns and requires explicit user confirmation. This ensures destructive commands are intercepted before execution in production.

Scanning commands before execution catches destructive patterns automatically, eliminating human error during manual review. A pre-execution hook inspects input for risky operations like rm -rf and enforces confirmation, preventing accidental data loss that manual review might miss.