freeze

Block Edit and Write actions outside a user-defined directory for the session.

Updated May 6, 2026
One-click install
npx skills add https://github.com/stayconnectquick/gstack --skill freeze-stayconnectquick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/stayconnectquick/gstack/tree/main/freeze
Command: npx skills add https://github.com/stayconnectquick/gstack --skill freeze-stayconnectquick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory within a session, preventing accidental or unintended changes outside the designated path.

Core Features & Use Cases

  • Blocks edits and writes outside the defined boundary, helping keep changes scoped to a module or folder.
  • Persists the boundary for the session via a state file and enforces the rule through a pre-tool hook.
  • Useful for debugging, code reviews, and experiments where you want to prevent spillover edits across the repository.

Quick Start

Provide the directory path to restrict edits to so that all edits remain inside that path.

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 bash session?

You can restrict edits to a specific directory by setting a boundary path that blocks any Edit or Write actions outside that folder for the current session. A pre-tool hook enforces this rule using a stored state file.

What is the best way to prevent accidental code changes outside a project boundary?

Preventing accidental changes outside a project boundary requires locking edits to a defined directory path. The lock applies across the workspace and uses a pre-tool hook to deny any out-of-bound modifications during the session.

Can I use a directory guardrail to stop writes outside a folder for code reviews?

Yes, applying a directory guardrail stops writes outside a specified folder, making it useful for code reviews and debugging. It ensures all session edits remain scoped to the target module without spillover.

How do I set up a session state file to enforce edit boundaries?

Setting up an edit boundary involves providing a target directory path to lock down. The system stores this boundary in a session state file and automatically enforces it via a pre-tool hook that denies out-of-bound changes.

Does the directory edit lock persist across different tools in the workspace?

The directory edit lock persists across the workspace for the current session by applying restrictions to both Edit and Write actions. It uses a state file to maintain the boundary and a hook to block unauthorized changes.