freeze

Restricts Edit and Write operations to a specified directory for the session.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill freeze-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/freeze
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill freeze-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When debugging or working in a large codebase, it is easy for an AI assistant to accidentally modify files outside the intended scope. This Skill enforces a hard boundary so Edit and Write operations outside a chosen directory are blocked, not just warned about. ## Core Features & Use Cases - Directory-scoped edit enforcement: A PreToolUse hook intercepts every Edit and Write call and denies any operation targeting a file outside the frozen directory. - Fail-closed design: Unparseable tool payloads, missing helpers, or unexpected hook failures all result in a deny decision, so the boundary never silently fails open. - Symlink-aware path resolution: Paths are resolved through their final component, so an in-boundary symlink pointing outside the boundary is checked against its real target. - Use Case: While debugging a bug in the src/auth module, freeze edits to that directory so the assistant cannot accidentally "fix" unrelated code elsewhere in the repository. ## Quick Start Ask the assistant to freeze edits to the directory you are working in, for example by saying "freeze edits to src/auth so nothing outside it can be modified".

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 one directory in a coding session?

Run the freeze command and provide the directory path when prompted. The skill resolves it to an absolute path, stores it in a state file, and a PreToolUse hook blocks every Edit or Write outside that path for the rest of the session.

How do I remove or change the edit freeze boundary?

Run the unfreeze command or simply end the session to remove the boundary. To change the frozen directory, run freeze again and provide a new path, which overwrites the stored state file.

Does the freeze boundary block Bash commands too?

No. The freeze hook only intercepts Edit and Write tool calls. Read, Bash, Glob, and Grep are unaffected, so shell commands like sed can still modify files outside the boundary. It prevents accidental edits, not a security boundary.

What happens if the freeze hook cannot parse a tool payload?

The hook fails closed: any payload it cannot parse is denied rather than allowed. A payload that parses but contains no file_path field is treated as a non-file tool and allowed through.

Can a symlink inside the frozen directory bypass the boundary?

No. The hook resolves symlinks through their final component before checking the path, so an in-boundary symlink pointing to a file outside the boundary is checked against its real target and denied.