freeze

To prevent accidental file edits outside a directory during debugging, you can apply a directory lock that blocks Edit and Write operations via pre-execution hook validation, restricting modifications strictly to your specified project folder.

Yes, you can restrict write operations to a single project folder without affecting read-only or command-line operations, as the edit blocking mechanism strictly targets Edit and Write tool invocations while leaving other actions untouched.

Scoped edit blocking is a mechanism that limits file modifications to a predefined boundary, needed during module workflows or debugging to ensure all changes stay within the intended folder and avoid unintended side effects to unrelated code.

To set up a directory lock to avoid modifying unrelated code, specify your allowed target directory in the prompt to activate pre-execution validation, which will automatically block any subsequent file edit operations targeting paths outside that boundary.

A limitation of restricting file edit operations to a user-specified directory is that the strict blocking applies only to Edit and Write tools, meaning unintended modifications could still occur through command-line operations executed within the workflow.

No, the freeze skill does not use soft warnings when blocking edits outside the allowed boundary, as it automatically enforces strict edit blocking on all Edit and Write operations targeting external paths with no override warnings.