guard

You can prevent destructive commands by enabling a directory-boundary guard that restricts edits to safe paths and requires explicit confirmation before irreversible actions like deletes or overwrites are executed.

Directory edit boundary enforcement is a workflow-security mechanism that restricts file modifications to a user-specified safe path, preventing accidental edits or destructive commands from impacting critical production data outside the boundary.

You can restrict file edits to a specific directory by enabling guard mode, which enforces a strict directory boundary and triggers warnings before any destructive or irreversible commands are executed outside the safe path.

Yes, guard mode seamlessly integrates with the careful and freeze hooks to provide end-to-end safety during debugging and maintenance, requiring no special code execution to activate real-time protections.

No special dependencies are required to enable destructive command warnings, as the guard mode operates without in-skill code execution and integrates directly with existing workflow hooks for real-time protection.

You should use a freeze boundary during development and production maintenance tasks where edits must be constrained to a safe path, ensuring that destructive commands require explicit confirmation before execution.