guard

Preventing accidental destructive shell commands during prod debugging requires a safety layer that intercepts dangerous actions like rm -rf or DROP TABLE and issues warnings before execution. This is achieved by enabling guard mode to enforce strict boundaries.

Yes, you can restrict file edits to a specific directory boundary by specifying your target path when enabling guard mode. The system confines all modifications to that directory, preventing any accidental or unauthorized edits outside the defined boundary.

The best way to warn before destructive actions like force-push or rm -rf is to activate a comprehensive guard mode that monitors shell commands and edits. It applies PreToolUse hooks to intercept and warn against dangerous operations automatically.

Yes, guard mode seamlessly integrates with existing careful and freeze workflows to provide a single, auditable safety guard. It coordinates with these sibling scripts to enforce both destructive command warnings and directory-bound edit restrictions simultaneously.

You need edit boundaries and destructive command warnings in system maintenance or prod debugging whenever strict safety is required across a directory. This prevents catastrophic data loss from dangerous shell commands and confines modifications to authorized paths.