freeze

Blocks Edit and Write operations on files outside a user-specified directory boundary.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill freeze-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/freeze
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill freeze-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When debugging or working in a large codebase, AI-assisted edits can accidentally touch unrelated files, causing unintended side effects. This Skill restricts all Edit and Write operations to a single directory you choose, so changes stay scoped to the module you are working on. ## Core Features & Use Cases - Edit Boundary Enforcement: A PreToolUse hook inspects every Edit/Write call and denies any operation targeting a file outside the frozen directory. - Session-Persistent State: The freeze boundary is stored in a state file and persists for the entire session until explicitly removed. - Path Safety: Trailing-slash normalization prevents sibling directories like /src-old from matching a /src boundary, and symlink/relative path resolution stops bypass attempts. - Use Case: While debugging a payment module, freeze edits to src/payments/ so the assistant cannot accidentally "fix" unrelated code in other parts of the repository. ## Quick Start Ask the assistant to freeze edits to a specific directory, for example: restrict all edits to the src/payments folder for this 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 one directory in a session?

Invoke the freeze skill and provide the target directory path when prompted. The path is resolved to an absolute path, stored in a state file, and every subsequent Edit or Write outside that directory is blocked until you unfreeze or end the session.

How does the freeze boundary check work?

A PreToolUse hook script reads the tool input JSON, extracts the file_path, resolves symlinks and relative segments, and compares it against the stored freeze directory. Paths outside the boundary receive a permissionDecision of deny.

Does freezing edits block Read, Bash, or Grep operations?

No. The freeze boundary applies only to Edit and Write tools. Read, Bash, Glob, and Grep are unaffected, which means commands like sed run through Bash can still modify files outside the boundary.

Is the freeze boundary a security sandbox?

No. It is a guardrail against accidental edits, not a security boundary. Shell commands executed through Bash bypass the hook, so it should not be relied on to prevent intentional modification of files outside the frozen directory.

How do I remove or change the freeze boundary?

Run the unfreeze skill or end the conversation to remove the restriction. To change the boundary to a different directory, run the freeze skill again and provide the new path, which overwrites the stored state file.