careful

To prevent accidental data loss from destructive commands like rm -rf or DROP TABLE, you need a safety check mechanism that validates user input and warns before execution. This Skill monitors and warns against these operations to protect system integrity.

The best way to add safety checks for destructive system commands in a shared environment is to use a monitoring tool that intercepts and validates commands before execution. This Skill applies to shared environments to ensure critical commands are not accidentally executed.

Yes, you can override safety warnings when you confirm a destructive command is intentional. This Skill includes a user override feature that allows you to proceed with confirmed actions after receiving the initial warning.

To guard against git reset --hard and other destructive operations on production systems, implement a validation layer that checks and validates user input before executing any command. This Skill acts as a safety net specifically for these high-risk environments.

This safety check mechanism applies to all environments where destructive operations are a risk, including production systems and shared development environments. It monitors commands like rm -rf, DROP TABLE, and git reset --hard across these contexts.

You should use a safety net for destructive commands because manual review is prone to human error, especially in complex production systems. This Skill provides automated monitoring and warnings, ensuring system integrity even when accidental commands are input.