freeze

Restrict Edit and Write tool inputs to a specified directory during Claude Code sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict accidental edits by locking modifications to a user-specified directory for the session, helping teams keep changes contained to a focused area of work.

Core Features & Use Cases

  • Restricts edits to a single directory during a session, blocking Edit and Write operations outside the boundary.
  • Syncs the boundary state to the brain so other agents can respect the scope.
  • Interactive setup prompts for the directory path and persists the boundary for the session.

Quick Start

Set a freeze boundary by selecting the directory to protect and let the skill enforce edits only within that path for the session.

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

You can restrict file edits by setting a boundary that blocks Edit and Write operations outside a designated directory, keeping all session changes scoped to that specific folder.

What is an edit boundary and how does it prevent code drift?

An edit boundary prevents code drift by acting as a directory lock that intercepts tool inputs, ensuring modifications only happen within the specified folder and blocking accidental edits elsewhere.

How do I lock a folder to prevent accidental edits in Claude Code?

To lock a folder in Claude Code, configure a PreToolUse hook that checks target paths against your specified directory, blocking any Edit or Write operations that fall outside the configured boundary.

Can I sync directory lock boundaries for team collaboration across multiple agents?

Yes, directory lock boundaries sync to the brain so multiple agents can respect the same edit scope, maintaining consistent collaboration boundaries during shared sessions.

Does the edit boundary persist across the entire session or do I need to reconfigure it?

The edit boundary persists for the entire session after interactive setup, continuously enforcing the directory lock without requiring reconfiguration until the session terminates.

What happens if a tool tries to modify a file outside the freeze boundary?

If a tool attempts to modify a file outside the freeze boundary, the PreToolUse hook checks the target path and blocks the Edit or Write operation to prevent scope drift.