guard

You can prevent unsafe edits by enabling directory-scoped freeze boundaries and descriptive warnings for destructive commands. This setup restricts modifications to a specified path and prompts before dangerous actions like rm -rf or DROP TABLE.

A directory-scoped edit freeze is a protection mechanism that restricts file modifications to a user-specified path. It enforces edit boundaries to ensure only approved directories are changed during critical workflows.

You set up destructive-command warnings by enabling careful protections that trigger prompts before dangerous actions. The system intercepts commands like force-push and DROP TABLE during pre-tool checks to require explicit confirmation.

Yes, you need the careful and freeze hooks installed and invoked during pre-tool checks. These sibling hooks provide the underlying enforcement for both the descriptive warnings and the directory-scoped edit boundaries.

Yes, you can restrict code modifications by applying a directory-bound edit freeze. This limits all edits exclusively to your user-specified path, preventing accidental changes to files outside the target directory.

Combining warnings with an edit freeze provides full safety mode by addressing both broad command risks and localized file modifications. Warnings prevent dangerous actions while the freeze enforces strict directory boundaries for comprehensive protection.