freeze

Block Edit and Write operations outside a specified directory boundary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the session to prevent accidental modifications to code outside the intended area.

Core Features & Use Cases

  • Lock edits and writes to a defined directory boundary during a session.
  • Provide a safe debugging environment by avoiding unintended changes to unrelated files.
  • Interact with users to set the boundary using prompts (AskUserQuestion) and enforce the boundary via PreToolUse hooks.

Quick Start

Set the freeze boundary to a specific directory to restrict edits within 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 boundary during a session?

To restrict edits to a directory boundary, you can lock modifications to a specific path using a boundary state file. This prevents unintended changes to files outside the intended area during your session.

What is the best way to prevent accidental writes to files outside my project folder?

Preventing accidental writes involves setting a directory boundary that blocks Edit and Write operations. This creates a safe debugging environment by avoiding unintended changes to unrelated files across local projects.

Do I need bash hooks to enforce directory edit restrictions?

Yes, enforcing directory edit restrictions requires Bash hooks and a boundary state file. These hooks intercept Edit and Write operations to enforce the specified boundary and report any violations.

Can I lock writes to a folder boundary while debugging code?

Yes, you can lock writes to a folder boundary to provide a safe debugging environment. This ensures that your debugging process avoids unintended changes to unrelated files outside the defined path.

How does a directory boundary block work for write operations?

A directory boundary block works by intercepting Edit and Write operations through PreToolUse hooks. When a write operation targets a path outside the boundary, the restriction is enforced and the violation is reported.