freeze

Block Edit and Write operations outside a predefined directory per session.

Updated Dec 17, 2025

Search Tags:#claude #session #hook #freeze #path-validation #edit-restriction

Ready to run

npx skills add https://github.com/eprouveze/HealthPulse --skill freeze-eprouveze

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Block edits to a specific directory during a session to prevent accidental modifications outside the intended scope, enabling safer debugging and controlled agent work.

Core Features & Use Cases

Session-scoped boundary: Establish a temporary edit limit for the duration of a Claude session.
Edit & Write protection: Block Edit and Write operations outside the allowed path while Read and other tools continue to function.
Automatic cleanup: Remove the boundary on session end or after a 24-hour grace period to avoid lingering locks.

Quick Start

Set the boundary directory and start the session to begin blocking edits outside that path.

Frequently Asked Questions about freeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I restrict Claude session edits to a specific directory?▼

You can restrict Claude session edits to a specific directory by applying a session-scoped boundary that validates target paths and blocks Edit and Write operations outside the allowed folder.

Can I read files outside the allowed path when edit restrictions are active?▼

Yes, you can read files outside the allowed path because the edit restriction only blocks Edit and Write operations, while Read, Bash, Glob, and Grep tools remain completely unaffected.

How does path validation work for blocking accidental file modifications?▼

Path validation works by using a boundary file and a small Bash hook to validate target paths, which emits a permissionDecision JSON whenever a Write or Edit operation violates the predefined directory boundary.

Do I need to manually remove the edit freeze boundary after debugging?▼

No, you do not need to manually remove the edit freeze boundary because it features automatic cleanup that removes the lock when the Claude session ends or after a 24-hour grace period.

What is the best way to scope agent debugging to prevent accidental changes?▼

The best way to scope agent debugging is to establish a temporary per-session freeze boundary that locks edits to a folder, ensuring controlled agent work without accidental modifications to external files.

Are there limitations to using a session-based freeze boundary for write protection?▼

A limitation of the session-based freeze boundary is that it only provides per-session write protection, meaning the edit lock is temporary and scoped strictly to the duration of that specific Claude session.