freeze

To restrict file edits to a single directory during debugging, you set a freeze boundary that blocks Edit and Write operations outside your chosen path while leaving Read, Bash, and Glob unaffected. This prevents accidental modifications to unrelated files.

Directory boundary guardrails for scoped refactoring are hooks that parse target file paths and return a deny decision for any out-of-scope modifications. They help ensure only the specific module being investigated or refactored is changed, reducing unintended side effects.

The freeze boundary does not affect Read, Bash, Grep, or Glob operations. It specifically intercepts and blocks only Edit and Write tool invocations that target files outside the user-defined directory boundary.

To set up a PreToolUse hook that blocks accidental file modifications, you run the freeze skill and provide the directory path you want to allow edits within. A state file then maintains this boundary for the entire session, checking every Edit and Write invocation.

You can maintain a scoped edit boundary across an entire coding session via a state file that persists your chosen directory path. The boundary is automatically checked on every Edit and Write tool invocation to ensure ongoing compliance.