freeze

Name: freeze
Availability: InStock
Author: ehsaanark

Restrict file edits to a chosen directory during interactive sessions.

Updated Mar 14, 2026

Search Tags:#development #debugging #tooling #session #freeze #prehook #edit-boundary

Ready to run

npx skills add https://github.com/EhsaanArk/ai-signal-router --skill freeze-ehsaanark

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/EhsaanArk/ai-signal-router/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/EhsaanArk/ai-signal-router --skill freeze-ehsaanark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces per-session edit boundaries by restricting file edits to a single, user-chosen directory, preventing accidental cross-project changes during debugging or focused development.

Core Features & Use Cases

Restrict edits to a designated directory for the duration of a session, blocking Edit and Write operations outside the boundary.
PreToolUse boundary checks run automatically before edit/write actions, with a clear denial message when outside the boundary.
Simple boundary setup through a guided prompt, enabling rapid isolation of changes to a single module or path.

Quick Start

Ask the user which directory to restrict edits to, then run the check-freeze.sh script to establish the boundary.

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, you establish a per-session edit boundary using a PreToolUse hook. This automatically blocks Edit and Write operations outside your chosen path, preventing accidental cross-project changes while debugging.

What are per-session edit boundaries and when do I need them?▼

Per-session edit boundaries limit file modifications to a single user-chosen directory for the duration of an interactive session. You need them when focusing on a single module or debugging to prevent accidental writes to other project paths.

How do I set up an edit boundary to isolate changes to a single module?▼

You set up an edit boundary by specifying your target directory through a guided prompt. Once designated, a shell script runs to establish the boundary, automatically enforcing write restrictions before any edit or write action occurs.

Does the edit boundary block both Edit and Write operations outside the saved path?▼

Yes, the edit boundary blocks both Edit and Write operations outside the saved path. The PreToolUse hook intercepts these actions automatically and returns a clear denial message if the target file is outside the boundary.

Can I isolate development changes to one folder without modifying my entire project structure?▼

Yes, you can isolate changes by locking edits to a session directory. This restricts writes to your specified folder without altering your underlying project structure, ensuring modifications remain contained during interactive development.