freeze

Restrict file edits to a designated directory during a session.

1|Updated Apr 6, 2026

Search Tags:#hook #freeze #edits #path-resolution #pretool-use #directory-boundary

Ready to run

npx skills add https://github.com/zhu637882-stack/jiaoyi --skill freeze-zhu637882-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/gstack-freeze
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill freeze-zhu637882-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the current session, blocking Edit and Write operations outside the allowed path to prevent accidental changes and to focus work on a module.

Core Features & Use Cases

Directory-boundary enforcement: Blocks edits outside the designated folder during a session.
Scoped debugging workflow: Use when debugging to prevent unintended changes across the codebase and to lock down edits to a single module.
Flexible activation: Works with interactive prompts to set the boundary at runtime.

Quick Start

Set the freeze boundary to a target directory and then attempt edits to verify that only files within that directory can be changed.

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

To restrict file edits to a single directory, you can lock edits to a specific folder using a PreToolUse hook. This enforces a directory boundary that denies Edit and Write operations outside the allowed path.

Can I prevent accidental code changes outside a specific module scope?▼

Yes, you can prevent accidental code changes by implementing directory-boundary enforcement. It blocks Edit and Write operations outside the designated folder, ensuring modifications stay within your target module scope.

How does a PreToolUse hook enforce path resolution boundaries?▼

A PreToolUse hook enforces path resolution boundaries by reading the freeze boundary from a state file. It intercepts tool calls and denies any Edit or Write operations targeting files outside that configured directory.

What is the best way to lock edits to a folder for a module-scoped task?▼

The best way to lock edits to a folder is by setting a freeze boundary at runtime through interactive prompts. This restricts modifications to the designated directory, preventing drift across the codebase.

Does directory-boundary enforcement work with dynamically set runtime paths?▼

Yes, directory-boundary enforcement supports flexible activation with interactive prompts. You can dynamically set the target directory path at runtime, and the hook will restrict edits to that specific folder.

Why are my Write operations being denied outside the freeze boundary?▼

Write operations are denied outside the freeze boundary because the PreToolUse hook actively blocks modifications outside the allowed path. It reads the allowed directory from a state file to prevent unintended file changes.