freeze

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill freeze-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/freeze
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill freeze-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When debugging or making scoped changes, it is easy to accidentally modify unrelated files outside the intended module. This Skill enforces a session-scoped edit boundary so that any Edit or Write operation targeting files outside the allowed directory is blocked, preventing accidental cross-module changes. ## Core Features & Use Cases - Directory-Scoped Edit Blocking: Uses PreToolUse hooks on Edit and Write tools to deny any file modification outside the configured freeze directory. - Session-Persistent Boundary: Stores the freeze path in a state file so the restriction applies consistently for the entire session. - Prefix-Safe Matching: Appends a trailing slash to the boundary path so /src does not accidentally match /src-old. - Use Case: While fixing a bug in the app/src/main module of an Android project, freeze edits to that directory so the AI cannot inadvertently touch build scripts, docs, or other modules during the debugging session. ## Quick Start Ask the assistant to freeze edits to the directory you are working in, for example by saying: restrict all edits to the app/src 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?

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

How do I block accidental edits outside a module while debugging?

Set a freeze boundary on the module directory before starting the debugging session. PreToolUse hooks check every Edit and Write call against the boundary and deny operations targeting files outside it.

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

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

How do I remove or change the freeze edit restriction?

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 boundary since it is session-scoped.

Is the freeze boundary a security sandbox?

No, it is a guardrail against accidental edits, not a security boundary. It only intercepts Edit and Write tool calls, so commands executed through Bash can still modify files anywhere on the filesystem.