freeze

Restrict file edits and writes to a specified directory for a session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module.

Core Features & Use Cases

  • Restricts Edit and Write outside the boundary, only allows within the frozen directory.
  • Persists for the session via a state file, enforced by pre-tool hook.
  • Useful during debugging to prevent accidental changes to other modules.

Quick Start

Ask the user which directory should I restrict edits to? Edits are now restricted to the provided 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 debugging session?

To restrict file edits to a specific directory during a debugging session, you can apply a runtime directory freeze. This blocks Edit and Write operations outside the allowed path to prevent accidental changes to unrelated modules.

Can I scope code changes to a single module to prevent accidental modifications elsewhere?

Yes, you can scope code changes to a single module by setting a boundary directory. This enforces a runtime freeze that persists for the session via a state file, ensuring all edits remain within the specified target path.

How does a pre-tool hook enforce a directory boundary for file writes?

A pre-tool hook enforces a directory boundary by checking file write operations against a configured state file. This shell hook intercepts edit attempts and restricts writes to within the frozen directory, maintaining session integrity across tools.

What's the best way to isolate module edits without altering unrelated code?

The best way to isolate module edits is by locking edits to a designated directory path. Using a pre-tool check script and shell hooks, this approach maintains session integrity by blocking any modifications outside the specified boundary.

Do I need a state file to maintain a directory freeze across different tools?

Yes, a configured state file is required to maintain a directory freeze across different tools. The state file persists the boundary directory configuration for the session, allowing the pre-tool check script to continuously enforce the edit restrictions.