freeze

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

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill freeze-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/freeze
Command: npx skills add https://github.com/adamtpang/summon.company --skill freeze-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging or working on a focused task, AI agents can accidentally modify unrelated files across the repository. This Skill prevents scope creep by hard-blocking any Edit or Write operation that targets files outside a directory you choose. ## Core Features & Use Cases - Edit Boundary Enforcement: A PreToolUse hook intercepts every Edit and Write call and denies it if the target file path falls outside the frozen directory. - Session-Persistent State: The freeze boundary is stored in a state file and persists for the entire session until removed with /unfreeze or session end. - Path Safety: Trailing-slash normalization prevents sibling directories like /src-old from matching a /src boundary, and symlink resolution ensures accurate path checks. - Use Case: While debugging a failing module, freeze edits to that module's directory so the agent cannot accidentally "fix" unrelated code elsewhere in the repo. ## Quick Start Ask the agent to freeze edits to a specific directory, for example by saying "freeze edits to the src/payments folder 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 session?

Invoke the freeze skill and provide the target directory when prompted. The skill resolves it to an absolute path, saves it to a state file, and a PreToolUse hook then blocks any Edit or Write outside that path for the rest of the session.

How do I remove or change the edit freeze boundary?

Run /unfreeze to remove the boundary entirely, or run /freeze again to set a new directory. Ending the conversation also clears the restriction since the boundary is session-scoped.

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 commands like sed run through Bash can still modify files outside the boundary. It prevents accidental edits, not malicious ones.

Why does the freeze directory need a trailing slash?

The trailing slash ensures prefix matching only blocks true path descendants. Without it, a boundary of /src would incorrectly match a sibling directory like /src-old, causing false denials or unintended allowances.

What happens if the freeze state file is missing or empty?

The hook script allows all operations when no freeze file exists or when it contains an empty path. It also fails open if the file_path cannot be parsed from the tool input, avoiding accidental blocking on parse errors.