freeze

Block file edits outside a user-specified directory during a session.

12|6|Updated Dec 2, 2025

Search Tags:#sandbox #freeze #development-workflow #safeguard #restrict-edits #directory-boundary

Ready to run

npx skills add https://github.com/shogo-labs/shogo-ai --skill freeze-shogo-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/shogo-labs/shogo-ai/tree/main/packages/agent-runtime/templates/virtual-engineering-team/.shogo/skills/gstack-freeze
Command: npx skills add https://github.com/shogo-labs/shogo-ai --skill freeze-shogo-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Block edits to a chosen directory to prevent accidental changes during debugging or development workflows.

Core Features & Use Cases

Dynamically set a directory boundary by prompting the user for a path and resolving it to an absolute path.
Enforce the boundary at Edit and Write tool invocations, blocking any attempt to modify files outside the allowed directory.
Persist the boundary for the session and provide a clear message when an operation attempts to cross the boundary.

Quick Start

Ask the assistant to set a freeze boundary by providing a directory path to restrict edits to that folder.

Frequently Asked Questions about freeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent accidental file edits outside a specific project directory?▼

To prevent accidental file edits outside a project directory, you can set a directory boundary that blocks Write and Edit actions. The boundary resolves your chosen path to an absolute directory and persists throughout the session.

What is a directory freeze boundary in a development workflow?▼

A directory freeze boundary is a safeguard that restricts file modifications to a single allowed directory. It intercepts Edit and Write tool invocations to block changes to files outside the resolved absolute path.

How do I restrict edits to a sandbox directory during debugging?▼

You restrict edits to a sandbox directory by prompting the assistant to set a freeze boundary with your chosen path. The system resolves the path to an absolute directory, appends a trailing slash, and saves it to a state file for ongoing enforcement.

Do I need to manually reapply the edit restriction for every file write in a session?▼

No, you do not need to manually reapply edit restrictions for every file write. Once you set the directory boundary, it persists across the entire session by saving the resolved absolute path to a state file for continuous enforcement.

Will I be notified when a file change attempts to cross the directory boundary?▼

Yes, you will be notified when a file change attempts to cross the directory boundary. The system provides a clear message whenever an Edit or Write operation targets a file outside the allowed directory during your session.

Can I use directory boundaries to safeguard against unwanted changes in large codebases?▼

Yes, you can use directory boundaries to safeguard against unwanted changes in large codebases. By restricting edits to a specific absolute path, the system blocks accidental modifications to files outside that chosen folder during development workflows.