freeze

Restricts edits to a defined directory using file-based session boundaries.

Updated Feb 24, 2026

Search Tags:#workflow #debugging #safety #directory #freeze #boundary #edits

Ready to run

npx skills add https://github.com/gaaschk/gaasch-family --skill freeze-gaaschk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/gaaschk/gaasch-family/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/gaaschk/gaasch-family --skill freeze-gaaschk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a user-defined directory for the session to prevent accidental changes outside the intended scope, especially during debugging or module-focused work.

Core Features & Use Cases

Block Edit and Write operations outside the configured boundary, keeping edits contained.
Persist a per-session freeze boundary and guide the user through setup with AskUserQuestion.
Deactivate by running /unfreeze or ending the session to restore normal editing.

Quick Start

Ask the user for a directory path to restrict edits to, then set the boundary for the current 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 session boundary that blocks Edit and Write operations outside your chosen directory, preventing unintended changes during focused debugging workflows.

Why would I need to lock edits to a single directory boundary?▼

Locking edits to a directory boundary prevents accidental modifications to files outside your intended scope, ensuring project safety during debugging or module-focused work.

How do I set up directory edit boundaries for debugging?▼

Setting up directory edit boundaries requires specifying a target path during your session, which triggers hook-based checks on Edit and Write operations and persists a boundary file for the current debugging workflow.

Can I deactivate the directory edit freeze after my session ends?▼

Yes, you can deactivate the directory edit freeze by running an unfreeze command or simply ending your current session, which restores normal editing capabilities across the entire project.

Does the edit freeze mechanism block write operations outside the configured scope?▼

Yes, the edit freeze mechanism applies hook-based checks to block both Edit and Write operations, returning a deny decision whenever an attempted change falls outside the user-defined directory boundary.

What happens to the boundary file when I restrict session edits?▼

When you restrict session edits, a per-session freeze boundary file is persisted to maintain the configured directory scope, ensuring that hook-based checks consistently enforce the edit limitations.