freeze

Restrict Edit and Write operations to a designated directory during a session.

Updated Mar 13, 2026

Search Tags:#debugging #freeze #safeguard #session-boundary #edit-control #directory-restriction

Ready to run

npx skills add https://github.com/soyasis/gstack-private --skill freeze-soyasis

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a designated directory for the current session, preventing drift and accidental changes.

Core Features & Use Cases

Define a persistent freeze boundary for a project
Block Edit and Write operations outside the allowed path
Useful during debugging or module isolation to confine changes
Boundary persists across the session and can be removed with /unfreeze
Note: This is a safety guard, not a security boundary; direct Bash commands can still modify files outside

Quick Start

Ask the user for a directory path to freeze and set the boundary so only edits within that path are allowed.

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 during a debugging session by setting a persistent freeze boundary that blocks Edit and Write operations outside a designated directory. This confines changes and prevents accidental drift to other project files.

What is a session-boundary edit control for module isolation?▼

A session-boundary edit control is a safeguard that confines file modifications to a specific project directory. It implements a runtime boundary using a PreToolUse hook to deny write operations outside the allowed path.

How do I set up directory restriction to prevent accidental file changes?▼

Set up directory restriction by providing a directory path to freeze, which establishes a persistent boundary for the session. The system then actively blocks any Edit or Write operations attempted outside that frozen directory.

Can I remove the directory freeze boundary after a debugging session ends?▼

Yes, you can remove the directory freeze boundary after a debugging session by using the /unfreeze command. The freeze is persistent across the session but can be easily removed when isolation is no longer needed.

Does the directory restriction safeguard block direct Bash commands?▼

No, the directory restriction safeguard does not block direct Bash commands. It functions as a safety guard against accidental drift via Edit and Write operations, not as a strict security boundary for shell commands.