freeze

You can restrict file edits to a specific directory by setting a boundary that blocks edit and write operations outside the allowed path. This persists for the session, preventing accidental modifications to unrelated code or modules during debugging.

Directory lock session management prevents accidental code changes by using a Bash script to check the boundary and a state file to persist the setting. It actively blocks edit and write operations outside the allowed directory for the duration of the session.

Yes, you need bash to restrict write operations to a specific project module. The Skill requires a Bash script to check the directory boundary and a state file to persist the session-specific setting that blocks edits outside the allowed path.

The best way to limit code safety boundaries to one directory per session is to use the `/freeze` command with the target path. This creates a session-specific restriction that blocks write and edit operations outside the specified directory.

You should use a directory edit restriction when debugging to avoid fixing unrelated code, or when you want to limit changes to one specific module. It ensures file edits are restricted to a specific directory for the entire session.