freeze

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

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill freeze-ulanxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/Ulanxx/mzstack/tree/main/freeze
Command: npx skills add https://github.com/Ulanxx/mzstack --skill freeze-ulanxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents edits from straying outside a designated directory during a session, helping maintain focus, reduce accidental changes, and make debugging safer.

Core Features & Use Cases

  • Restricts edits to the specified directory for the session.
  • Provides a PreToolUse hook that checks Edit/Write operations and blocks outside boundary.
  • Persists the boundary across the session via a state file so it remains active until reset.

Quick Start

Ask the user for a directory, then set the boundary to that path using the /freeze command.

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 freeze boundary that blocks any modifications outside the designated path. This enforces scope control and prevents accidental drift during focused work.

How do I prevent accidental edits outside a specific folder while debugging?▼

To prevent accidental edits outside a folder, a PreToolUse hook checks file operations and denies modifications beyond the boundary. This ensures debugging changes remain scoped to the target module.

What is a PreToolUse hook for blocking file modifications?▼

A PreToolUse hook for blocking file modifications intercepts edit and write operations before execution, checking them against a persistent state file to deny any changes outside a set directory boundary.

Can I lock edits to a single module and persist that boundary across a session?▼

Yes, you can lock edits to a single module and persist that boundary across a session. A state file maintains the restriction until explicitly reset, keeping the scope active throughout your workflow.

Does the freeze boundary work without additional dependencies?▼

Yes, the freeze boundary works without additional dependencies. It relies solely on a persistent state file and a PreToolUse hook to enforce directory restrictions, requiring no external components.

When should I not use a directory freeze boundary for scoping changes?▼

You should not use a directory freeze boundary when your task requires editing multiple modules or making cross-directory references. It is designed for isolated debugging and restricts all edits outside the specified path.