freeze

To restrict file edits to a specific directory, you can lock a freeze boundary to that path for your current session. This prevents accidental modifications to files outside the designated directory.

Preventing accidental code modifications outside a project scope is achieved by binding a directory boundary to your session. The boundary verifies file paths and blocks Write or Edit operations outside the specified directory.

Restricting edits to a directory does not block shell commands or file reading. The freeze boundary only applies to Edit and Write tool operations, allowing Read operations and external shell commands to function normally.

You can use directory edit locking to enforce scope during debugging sessions. By restricting edits to a designated directory, you reduce accidental modifications to other modules while investigating issues.

A session enforces a directory freeze boundary by storing the path in a session state file. It then verifies the file_path against this stored boundary for every edit attempt before allowing the operation.

You need git and python3 installed to lock directory edits in your session. The skill also relies on grep, sed, basename, and date dependencies to manage and verify the session state file.