freeze

Deny Edit and Write operations targeting paths outside a selected directory.

8|2|Updated Mar 24, 2026

Search Tags:#debugging #guardrails #freeze #scoped edits #tool hooks #path restriction

Ready to run

npx skills add https://github.com/MFS-code/gstack --skill freeze-mfs-code

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents accidental edits outside a chosen scope by blocking Edit and Write operations that target files outside a user-defined directory, helping you safely debug or confine changes to one module.

Core Features & Use Cases

Directory-scoped edit enforcement: Denies Edit/Write attempts when the target file path is outside the frozen boundary.
Manual trigger control: Intended for invocation only when the user explicitly types /freeze.
Persistent session boundary: Stores the selected directory in a state file and checks it on every Edit/Write call.

Quick Start

Ask your agent: /freeze and tell it the directory you want to restrict edits to (for example, /path/to/your/module/).

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 debugging?▼

Restricting file edits to a single directory during debugging involves setting a persisted freeze boundary via a PreToolUse hook that checks file paths and denies any Edit or Write operations outside your chosen folder.

How can I prevent accidental file modifications when refactoring a specific module?▼

Preventing accidental file modifications when refactoring requires enforcing a scoped edit boundary that intercepts tool operations and returns a deny decision for any target path outside your designated directory.

What are tool hooks and how do they enforce path restrictions for scoped edits?▼

Tool hooks enforce path restrictions for scoped edits by intercepting Edit and Write calls, checking target file paths against a stored directory boundary, and denying permission for any violations detected during the session.

Can I confine code changes to one folder for a current session only?▼

Yes, you can confine code changes to one folder for a current session by setting a persistent freeze boundary that stores your selected directory and validates every Edit and Write operation against that path for the duration of your work.

Does this directory freeze boundary block both Edit and Write tool operations?▼

Yes, the directory freeze boundary blocks both Edit and Write tool operations by applying a PreToolUse hook that performs path checks and returns a deny permission decision for any file outside the frozen directory.

When should I use directory-scoped edit enforcement?▼

You should use directory-scoped edit enforcement during debugging and scoped refactors when you need to safely confine changes to one folder, preventing accidental edits to files outside the chosen module.