freeze

Restrict file edits to a designated directory during a session.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill freeze-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/freeze
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill freeze-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits".

Core Features & Use Cases

  • Restrict edits to a designated directory for the current session.
  • Prevent accidental changes across modules during debugging or code reviews.
  • Apply quickly to maintain focused, safe edits in large codebases.

Quick Start

Set the freeze boundary to a specific directory to restrict edits to that folder.

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 a specific directory during a coding session?

You can restrict file edits by setting a directory boundary that denies Edit and Write operations outside the allowed path. This prevents accidental changes to unrelated code during interactive development workflows.

How can I prevent accidental code changes outside a designated folder while debugging?

Preventing accidental code changes outside a designated folder while debugging is achieved by applying a persisted boundary file and a pre-edit hook. This mechanism denies edits beyond the designated directory in real-time.

Does the edit restriction boundary handle both absolute and relative file paths?

Yes, the edit restriction boundary handles both absolute and relative file paths. It applies path normalization within its pre-edit hook to accurately verify and deny Write or Edit operations outside the designated directory.

What is the best way to lock down edits to a single module in a large codebase?

The best way to lock down edits to a single module in a large codebase is to freeze edits to a folder for the session. This scopes your changes by applying a boundary that blocks modifications across other modules.

Can I scope changes to one directory without modifying files outside the boundary?

Yes, you can scope changes to one directory without modifying files outside the boundary. The tool implements a pre-edit hook that actively denies any Edit or Write operations attempting to modify files beyond the set boundary.

When should I use a directory edit freeze in my development workflow?

You should use a directory edit freeze during debugging or code reviews to prevent accidentally fixing unrelated code. It is ideal when you need to scope changes to one module and maintain focused, safe edits in large codebases.