gstack-guard

To prevent destructive commands during production debugging, enable a safety mode that detects high-risk operations like rm -rf, DROP TABLE, and force-push, warning you before execution. This allows you to override intentionally while protecting the live system.

Yes, you can restrict file edits to a specific directory by enforcing directory-scoped edit freeze boundaries. This blocks any read, edit, or write operations outside your chosen path, preventing accidental broad filesystem damage during maintenance.

Guard mode is a full safety configuration for incident prevention that combines destructive-command warnings with directory-scoped edit restrictions. It runs pre-tool checks for destructive commands and enforces freeze-boundary checks on file operations to ensure safe workspace iteration.

To activate directory freeze boundaries, initiate guard mode and provide the specific directory path you want edits restricted to. The system then enforces freeze-boundary checks for any subsequent read, edit, or write operations within that workspace.

Yes, guard mode is explicitly designed for production-adjacent maintenance and live-system debugging. It restricts file edits to a user-specified path and warns on high-risk operations, ensuring you can safely iterate without risking broader filesystem or database damage.

Filesystem protection warnings catch high-risk operations such as rm -rf, DROP TABLE, and force-push. When these destructive commands are detected, the system warns you so you can override the action intentionally and prevent accidental data loss.