freeze

Restrict Edit and Write operations to a specified directory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, git.

What problem does it solve?

Prevents accidental or out-of-scope file edits by restricting Edit and Write operations to a single directory for the session, reducing risk during debugging, focused development, or code review.

Core Features & Use Cases

  • Session-scoped edit boundary: Persistently records a freeze directory so all subsequent Edit/Write tool calls are checked against it.
  • PreToolUse enforcement: A hook script validates file paths and returns a permissionDecision deny for operations outside the allowed path, blocking edits (not just warning).
  • Practical uses: Limit changes to a single module while debugging, enforce a temporary code freeze during reviews, or allow contractors to modify only a subdirectory.
  • Behavior notes: Read and Bash tools are unaffected by the freeze guard, and the hook uses path normalization and symlink resolution to avoid bypasses; this is a safety guard, not an absolute security boundary.

Quick Start

Set the freeze boundary to /project/src so that edits are only allowed inside that folder.

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

You can restrict file edits to a specific directory by setting a persistent freeze boundary that validates Edit and Write tool paths against an allowed directory and denies modifications outside of it.

Can I prevent out-of-scope file modifications during code reviews?

Yes, you can prevent out-of-scope file modifications during code reviews by applying a PreToolUse hook that returns a deny permission decision for any Edit or Write operation targeting paths outside a configured freeze directory.

Do I need Python3 and Git to use directory edit restrictions?

Yes, Python3 and Git are required dependencies for running the PreToolUse hook script that validates file paths and enforces the directory edit restrictions.

Does the freeze guard block Bash commands and read operations?

No, the freeze guard does not affect Bash or Read tools; it exclusively restricts Edit and Write tools from modifying files outside the specified freeze directory.

What happens if a file path uses symlinks to bypass directory edit restrictions?

The hook script applies path normalization and symlink resolution when validating file paths, preventing symlink bypasses from allowing edits outside the allowed freeze boundary.

What are the limitations of using a PreToolUse hook for file edit restrictions?

The PreToolUse hook for file edit restrictions acts as a safety guard rather than an absolute security boundary, reducing accidental modification risk during debugging without guaranteeing complete security.