freeze

Block Edit and Write operations outside a defined directory boundary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lock edits to a directory during a session to prevent accidental changes outside a scoped area, reducing risk when debugging or focusing work.

Core Features & Use Cases

  • Enforces directory-bound edits, blocking Edit and Write operations targeting files outside the allowed path.
  • Provides a simple setup flow to define the freeze boundary and persist it for the session.
  • Supports scoped changes during debugging or when you want to limit impact to a single module.

Quick Start

Provide the target directory path to freeze edits and run the freeze command to activate.

Frequently Asked Questions about freeze

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

FAQPage Schema
How do I lock file edits to a specific directory during debugging?

To lock file edits to a specific directory during debugging, you set a freeze boundary by providing the target directory path and running the freeze command, which blocks Edit and Write operations outside that path.

What is the best way to prevent accidental changes to files outside a scoped area?

The best way to prevent accidental changes outside a scoped area is to activate a directory boundary that normalizes target paths and denies any Edit or Write operations falling outside the defined freeze boundary.

Can I restrict Edit and Write operations to a single module for a session?

Yes, you can restrict Edit and Write operations to a single module by setting a freeze boundary. The system reads the boundary from a persistent state file and enforces directory-bound edits throughout the session.

How does a directory boundary block file modifications?

A directory boundary blocks file modifications by normalizing the target path of an Edit or Write operation and denying the request if the normalized path falls outside the persisted freeze boundary.

Do I need to manually check file paths before editing when a freeze boundary is set?

No, you do not need to manually check file paths. Once the freeze boundary is activated, the system automatically reads the boundary from a persistent state file and blocks edits to files outside the allowed directory.

Why are my file edits being denied during a debugging session?

Your file edits are being denied because the target path falls outside the defined freeze boundary. The system normalizes target paths and blocks Edit or Write operations targeting files outside the allowed directory boundary.