freeze

Block Edit and Write operations outside a user-defined directory.

Updated Mar 24, 2026

Search Tags:#development #debugging #directory #freeze #boundary #edits

Ready to run

npx skills add https://github.com/pistosmin/base-one --skill freeze-pistosmin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/pistosmin/base-one/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/pistosmin/base-one --skill freeze-pistosmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a user-defined directory for the current session to prevent accidental changes outside the intended area.

Core Features & Use Cases

Blocks Edit and Write operations outside the specified boundary during a debugging or focused development session.
Enforces a configurable freeze boundary via a PreToolUse hook that evaluates the target file path.
Suitable for scoping changes to a single module or directory during critical edits.

Quick Start

Provide a directory path to freeze, and the skill will enforce edits only within that boundary for the 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 a single directory during a debugging session?▼

To restrict file edits to a single directory during a debugging session, you can define a freeze boundary file that blocks all Write and Edit operations outside that specified path. This prevents unintended changes to other modules.

What is a freeze boundary and how does it prevent unintended code changes?▼

A freeze boundary is a user-defined directory limit evaluated by a PreToolUse hook. It prevents unintended code changes by intercepting file operations and blocking any edits that target paths outside the configured boundary.

How do I set up a PreToolUse hook to block writes outside a specific project folder?▼

You set up a PreToolUse hook to block writes outside a specific project folder by configuring a check-freeze script that evaluates target file paths against your defined boundary. This script enforces the directory limit for the session.

Can I scope focused development tasks to one module without affecting other directories?▼

Yes, you can scope focused development tasks to one module without affecting other directories by applying a session freeze. This configuration confines all modifications strictly to your chosen folder, safeguarding the rest of the project.

Does freezing a directory block both file writes and edits during a session?▼

Yes, freezing a directory blocks both file writes and edits during a session. The enforcement mechanism intercepts these specific operations, ensuring no modifications occur outside the user-defined boundary.

When should I not use a directory freeze for my development workflow?▼

You should not use a directory freeze when your development workflow requires modifying multiple modules or directories simultaneously. The boundary strictly blocks all operations outside the single configured folder for the entire session.