freeze

Block file edits and writes outside a user-specified directory during a session.

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

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. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". (gstack)

Core Features & Use Cases

  • Boundary enforcement: Blocks edits outside the configured directory to keep changes contained.
  • Interactive setup: Uses AskUserQuestion to capture the directory to freeze.
  • Session persistence: Persists the boundary in a state file to survive across actions during the session.
  • Use Case: During debugging, lock edits to a single module to avoid accidental drift.

Quick Start

Ask the user for the directory to restrict edits to, then set the boundary and begin enforcing it.

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?

Restricting file edits to a directory prevents accidental modifications to unrelated code. You freeze edits to a target folder using a PreToolUse hook, ensuring all changes remain confined to that path for safe debugging.

How do I lock down changes to only one folder in my codebase?

Locking down changes to one folder requires setting an edit boundary. You interactively specify the target directory, and a persistent state file enforces the restriction across actions, blocking writes outside that module.

How does a PreToolUse hook prevent accidental edits outside a target directory?

A PreToolUse hook prevents accidental edits by checking file paths against a persisted boundary file before tool execution. If the path falls outside the allowed directory, the edit or write operation is blocked.

Can I scope modifications to a single module without affecting the rest of the project?

Yes, you can scope modifications to a single module by setting a session boundary. This confines all write operations to your specified directory, preventing drift and protecting the rest of the project from accidental changes.

Does the edit boundary persist across different actions during a focused work session?

Yes, the edit boundary persists across actions during a session. It saves the specified directory restriction in a persistent state file, ensuring safeguards remain active until your debugging or focused work is complete.