freeze

Restrict Edit and Write operations to a designated directory via a PreToolUse hook.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/diiviikk5/rezops --skill freeze-diiviikk5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/diiviikk5/rezops/tree/main/freeze
Command: npx skills add https://github.com/diiviikk5/rezops --skill freeze-diiviikk5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the session. Prevents edits outside the allowed path, reducing the risk of accidental changes during debugging or scoped development.

Core Features & Use Cases

  • Boundary-based edit blocking: confines Edit and Write operations to a user-selected directory.
  • Read/inspect flexibility: Read operations remain unrestricted to allow visibility without modification.
  • Workflow scoping: ideal when debugging or when changes should be limited to a single module or folder.

Quick Start

Tell me to restrict edits to a directory by running the /freeze command with the target path.

Frequently Asked Questions about freeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restrict file edits to a specific directory during a development session?

You can restrict file edits to a specific directory by setting a directory boundary that blocks Edit and Write operations outside the chosen path. This confines modifications to a single folder while keeping Read operations unrestricted for full visibility.

What is a PreToolUse hook for blocking file modifications outside a project folder?

A PreToolUse hook is a safety mechanism that intercepts Edit and Write operations before execution, reading a defined boundary from a state file to deny any file modifications targeting paths outside a designated directory.

Can I still read files outside the allowed directory boundary when edit restrictions are active?

Yes, you can still read files outside the allowed directory boundary when edit restrictions are active. The freeze hook specifically blocks Edit and Write operations, leaving Read operations completely unrestricted to allow inspection without modification risks.

How do I confine code changes to a single module to prevent accidental edits elsewhere?

You can confine code changes to a single module by applying a directory boundary that restricts file edits to a chosen path. This blocks Write and Edit operations outside the folder, ensuring safe scoped debugging without accidental modifications.

Does the directory boundary edit restriction work for both Write and Edit operations?

Yes, the directory boundary edit restriction works for both Write and Edit operations. The safety hook intercepts both actions, checking the file path against the allowed boundary and denying any operation that falls outside the designated directory.