freeze

Restricts file edits to a user-specified directory via a PreToolUse hook.

Updated Apr 3, 2026

Search Tags:#validation #directory #hook #freeze #boundary #edits #safeguards

Ready to run

npx skills add https://github.com/lyh2/gstack-deepseek --skill freeze-lyh2

💬 Prompt for ChatGPT / Claude Chat▼

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

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

Lock edits to a directory for the duration of a session, preventing changes outside the boundary.
PreToolUse hook checks the target path and blocks edits outside the allowed directory.
Useful for debugging or scoped changes to a single module or folder.

Quick Start

Tell me which directory to freeze and I will set the edit boundary accordingly.

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 debugging session?▼

You can restrict file edits by setting a directory freeze boundary, which uses a PreToolUse hook to validate target file paths and deny edit operations attempted outside the specified folder.

How does a PreToolUse hook prevent unintended changes outside a module boundary?▼

A PreToolUse hook prevents unintended changes by validating the target file path against a stored directory boundary before any edit operation executes, automatically denying access to files outside the allowed folder.

Can I lock down edits to a single folder when working on scoped development tasks?▼

Yes, you can lock down edits to a single folder by specifying the target directory, which restricts all session changes to that boundary and prevents accidental modifications to unrelated code modules.

What is the best way to scope code changes to one module without affecting unrelated files?▼

The best way to scope code changes to one module is to freeze the directory boundary, which enforces a strict edit perimeter and blocks any write operations attempted on files outside that specific folder.

Does the directory freeze boundary block both Write and Edit operations?▼

Yes, the directory freeze boundary blocks both Write and Edit operations, validating the target path of each requested change against the stored boundary to ensure no modifications occur outside the allowed directory.

When should I restrict edits to a specific directory boundary during development?▼

You should restrict edits to a specific directory boundary when debugging to prevent accidentally fixing unrelated code, or when you need to strictly scope development changes to a single module or folder.