freeze

Block Edit and Write operations outside a configured directory boundary.

Updated Apr 12, 2026

Search Tags:#debugging #freeze #session-boundary #workflow-safety #directory-boundary #edit-control

Ready to run

npx skills add https://github.com/adryanmoldokkr32-pixel/gstack --skill freeze-adryanmoldokkr32-pixel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/adryanmoldokkr32-pixel/gstack/tree/main/freeze
Command: npx skills add https://github.com/adryanmoldokkr32-pixel/gstack --skill freeze-adryanmoldokkr32-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the current session, blocking Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". (gstack)

Core Features & Use Cases

Restrict edits to a single directory for the current session.
Block Edit and Write operations outside the boundary.
Use case: while debugging a module, freeze boundary ensures only that module is modified, avoiding unintended changes elsewhere.

Quick Start

Ask me for the directory to freeze, then apply the boundary with /freeze.

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 single directory during a debugging session?▼

You can restrict file edits by applying a directory boundary that uses a PreToolUse hook to check target file paths and block Write or Edit operations outside the allowed folder for the current session.

What is session-boundary edit control and how does it prevent unintended code changes?▼

Session-boundary edit control is a workflow safety mechanism that prevents unintended code changes by locking modifications to a defined folder, ensuring debugging or module isolation does not impact unrelated files elsewhere.

How do I lock down edits to only one folder for my current workflow?▼

You lock down edits by specifying a target directory to freeze, which applies a state file boundary that denies any Edit or Write operations targeting file paths outside that specific folder.

Does edit control work by blocking Write operations outside a specified path?▼

Yes, edit control blocks Write operations by using a PreToolUse hook to evaluate the target file path against a stored boundary, denying any attempt to modify files outside the defined directory.

When should I use a directory boundary to isolate module modifications?▼

Use a directory boundary to isolate module modifications when debugging or scoping changes to a single folder, preventing accidental edits to unrelated code in other parts of the project.

What are the limitations of freezing edits to a directory for a session?▼

The limitation of freezing edits is that the boundary restricts all Write and Edit operations to a single folder for the entire session, meaning any required modifications outside that path will be denied until the boundary is removed.