freeze

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

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill freeze-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/freeze
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill freeze-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging or working on one module, AI-assisted edits can accidentally modify unrelated files across the repository. This Skill restricts Edit and Write operations to a single directory, blocking any change outside the allowed path for the session. ## Core Features & Use Cases - Directory-Scoped Editing: Sets a freeze boundary so Edit and Write tools only work inside the chosen directory. - PreToolUse Hook Enforcement: A Bash hook inspects each Edit/Write call's file path and returns a deny decision for out-of-boundary targets. - Session-Persistent State: Stores the freeze directory in a state file so the boundary applies to every subsequent edit until removed. - Use Case: While debugging a failing module in src/auth/, freeze edits to that folder so the AI cannot accidentally "fix" unrelated code elsewhere in the repo. ## Quick Start Ask the assistant to freeze edits to a specific directory, for example: restrict all edits to the src/auth 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 AI code edits to one directory?

Run the freeze command and provide the target directory path when prompted. The skill saves the absolute path to a state file, and a PreToolUse hook blocks any Edit or Write operation targeting files outside that directory.

How do I block Edit and Write tool calls outside a folder?

The freeze skill registers a PreToolUse hook that reads the file_path from each Edit or Write tool call and returns a permissionDecision of deny when the path falls outside the frozen directory. Allowed paths return an empty decision.

Does the freeze boundary affect Read, Bash, or Grep tools?

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

Is the freeze skill a security boundary for untrusted code?

No, it is designed to prevent accidental edits, not to enforce security. Shell commands executed through Bash can bypass the hook, so it should not be relied on as a sandbox or access control mechanism.

How do I remove or change the freeze directory?

Run the freeze command again to set a new boundary directory, or run the unfreeze command to remove the restriction entirely. Ending the session also clears the freeze state.