freeze

You can block edits outside a directory by setting a session-wide boundary. The Skill intercepts Edit and Write operations via a pre-tool hook, returning a denial whenever a file path lies outside your designated workspace safeguard.

Yes, you can prevent unintended changes by freezing a specific directory boundary. It restricts Edit and Write operations to within the approved path, safeguarding unrelated code while you debug or experiment locally.

Session edit control persists by storing the allowed directory path in a dedicated state file. This ensures the edit-block boundary remains active and enforces restrictions continuously until the current session ends.

The best way to restrict Write operations is by enforcing a strict boundary that intercepts modification attempts. A pre-tool hook checks the target path against an approved directory, returning a denial for any file outside that boundary.

You should use a directory freeze boundary when debugging a specific module or testing new changes in a controlled area. It minimizes collateral edits by preventing unintended changes to unrelated parts of the repository during rapid iteration.