freeze

Restrict Edit and Write operations to a user-defined directory for a session.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Prestonigo/Claude-Skills --skill freeze-prestonigo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/Prestonigo/Claude-Skills/tree/main/gstack-main/freeze
Command: npx skills add https://github.com/Prestonigo/Claude-Skills --skill freeze-prestonigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lock edits to a specific directory for the session to prevent accidental changes outside the allowed path. This is helpful during debugging or when you want to confine changes to a single module.

Core Features & Use Cases

  • Enforces a live boundary: stores a per-session directory boundary and blocks edits outside it.
  • Works with Edit and Write operations to keep accidental edits in check during development.
  • Use Case: while debugging a module, freeze edits to that module's folder to avoid unintended changes elsewhere.

Quick Start

Ask the user for a directory path to restrict edits to, then save and enforce the boundary for the session.

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 coding session?▼

To restrict file edits to a specific directory during a coding session, you can freeze edits by defining a target folder path, which establishes a persisted boundary that blocks any Edit or Write operations outside that allowed directory.

Can I lock edits to a single module folder to prevent unintended changes while debugging?▼

Yes, you can lock edits to a single module folder during interactive debugging. This enforces a live boundary that blocks Edit and Write operations outside the specified directory, preventing unintended changes to the rest of your project.

What is the best way to isolate changes to a specific directory boundary in my workflow?▼

The best way to isolate changes to a specific directory boundary is to freeze the session to a single path. The tool evaluates your tool input path against a persisted boundary and blocks edits outside that folder.

How does a directory boundary block work when editing files?▼

A directory boundary block works by evaluating the tool input path against a user-defined folder and blocking Edit or Write operations outside that boundary. This restricts edits to a specific directory during an interactive session.

Do I need to manually configure dependencies to freeze edits in a folder?▼

No, you do not need to configure dependencies to freeze edits in a folder. The tool operates independently by asking for a directory path, saving the boundary, and enforcing it for the session without requiring external components.

Why are my edits being blocked outside the allowed directory path?▼

Your edits are being blocked outside the allowed directory path because a session boundary has been frozen. This restriction prevents unintended changes by blocking Edit and Write operations for any tool input path outside the defined directory.