freeze

Run the freeze command and provide the target directory path when prompted. The skill saves the absolute path to a state file, and a PreToolUse hook then blocks any Edit or Write operation targeting files outside that directory for the rest of the session.

Run the /unfreeze command or simply end the conversation session. The freeze boundary is stored in a session state file, so it does not persist beyond the session unless explicitly set again.

No. The freeze hook only intercepts Edit and Write tool calls. Bash commands such as sed can still modify files outside the boundary, so freeze is a guardrail against accidental edits, not a security boundary.

The skill appends a trailing slash to the freeze directory before comparison, so the prefix check only matches paths genuinely inside the directory. This prevents sibling directories with similar names like /src-old from being incorrectly included.

The hook script allows all Edit and Write operations when no freeze file exists or the stored path is empty. It also fails open if the file path cannot be parsed from the tool input, avoiding accidental blocking on parse errors.