guard

To prevent accidental destructive commands during production debugging, this safety mode intercepts and warns before executing operations like rm -rf or force-push. It enforces runtime safety rails to block unauthorized actions in critical environments.

The best way to enforce directory-scoped edit protection is by applying a configurable edit boundary at runtime. This restricts file modifications to approved directories, preventing unscoped edits during sensitive sysadmin tasks.

Yes, you can combine destructive command warnings with cross-directory edit restrictions. This unified safety mode integrates the capabilities of careful and freeze hooks to provide complete protection for risk-sensitive changes.

You need full safety rails for code maintenance when executing operations where destructive actions and cross-directory edits must be warned or blocked. This prevents catastrophic data loss during critical production debugging and modifications.

Yes, this safety mode works with the careful and freeze hooks. It implements direct integration with these sibling hooks to combine destructive-command warnings and directory-scoped edit protections into a single unified mode.

To enable full safety mode and block unauthorized file edits, you run the guard command. This applies both destructive-command warnings and directory-scoped edit protections immediately to your environment.