freeze

Block Edit and Write operations outside a user-specified directory.

37|2|Updated Mar 28, 2026

Search Tags:#bash #macos #freeze #directory-boundary #edit-restriction #pretool-hook

Ready to run

npx skills add https://github.com/DariusCorvus/iqualize --skill freeze-dariuscorvus

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict 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

Lock edits to a single directory during a session to prevent accidental changes outside the target path.
Supports debugging workflows by confining edits to a safe zone, reducing risk of unintended modifications.
Works with pre-tool hooks to enforce the boundary transparently.

Quick Start

Ask the user for the directory to freeze and apply an edit boundary 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 lock edits to a specific directory during a debugging session?▼

To lock edits to a directory, you apply an edit boundary that blocks Edit and Write operations outside the allowed path, preventing accidental modifications to unrelated code during interactive debugging.

What is directory-boundary edit restriction in bash workflows?▼

Directory-boundary edit restriction is a mechanism that confines file modifications to a single user-specified path, ensuring changes remain scoped to one module and reducing the risk of unintended changes.

How do I prevent Write and Edit operations outside a target path on macOS?▼

You can prevent Write and Edit operations outside a target path by using a pretool hook to transparently enforce a boundary file, checking every edit request against the allowed directory.

Does the freeze edit restriction work with pre-tool hooks?▼

Yes, the edit restriction works transparently with pre-tool hooks to enforce the directory boundary, blocking any attempts to modify files outside the defined safe zone during the session.

What are the limitations of scoping edits to a single directory?▼

The limitation of scoping edits to a single directory is that the boundary relies on a stored file at ~/.gstack/freeze-dir.txt, meaning the restriction is confined to the active session and a single allowed path.