freeze

The 'freeze' skill is designed to restrict file editing to a specific directory during an active session. By setting a freeze boundary, it blocks any Edit or Write operation targeting files outside the designated path, effectively preventing accidental changes to unrelated code. This is particularly useful during debugging or focused development, where maintaining control over which parts of a codebase can be modified is critical. The skill ensures that developers can confidently work within a specific module or folder without unintentionally affecting other areas of a project.

Key features of the 'freeze' skill include interactive setup for selecting the target directory, automatic resolution to an absolute path, and persistence of the freeze boundary for the duration of the session. The skill performs safety checks for all Edit and Write operations, denying any attempt to modify files outside the allowed path. It also preserves the directory structure carefully, using a trailing slash to avoid partial matches, and logs skill usage for tracking. While the restriction applies strictly to Edit and Write tools, Read and other operations like Bash or Grep remain unaffected, making it a practical tool for scoped modifications without interrupting other development tasks.

Use cases for this skill include debugging sessions, module-specific development, and scenarios where code review or testing requires isolation of changes. Target users include developers, code reviewers, and technical leads who need to enforce temporary editing boundaries. It is suitable for teams working in shared repositories or complex projects where accidental edits could introduce errors. By clearly defining the edit scope, the skill helps maintain code integrity and reduces the risk of unintended modifications.