freeze

Blocks edits and writes to files outside a user-specified directory via hook enforcement.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Faeif/linguaquest --skill freeze-faeif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/Faeif/linguaquest/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/Faeif/linguaquest --skill freeze-faeif

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

  • Freeze editing boundary to a directory during a session, blocking any edits outside.
  • PreToolUse hook and boundary check to enforce the restriction during Edit/Write.
  • Works for debugging and module-scoped changes; preserves state across the session.

Quick Start

Ask the user for a directory to restrict edits to, then persist the boundary and begin blocking edits outside it.

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?

To restrict file edits to a specific directory, you can freeze the editing boundary for your session. This blocks Edit and Write operations outside the allowed path, preventing accidental changes to unrelated code while debugging.

Can I lock down edits to a single folder for module-scoped development?

Yes, you can lock down edits to a single folder for module-scoped development. By establishing a boundary, a pre-tool hook denies any edit operations outside that specific directory, ensuring your changes remain isolated to the target module.

How does a pre-tool hook enforce an edit boundary for file operations?

A pre-tool hook enforces an edit boundary by intercepting file operations before they execute. It checks the target path against a user-specified directory and denies any Edit or Write commands that fall outside the established boundary.

Does the edit freeze boundary persist across the entire session?

Yes, the edit freeze boundary persists across the entire session. The restriction state is saved via a state file, ensuring the directory lock remains active and blocks out-of-scope edits continuously until the session ends.

What is the best way to prevent accidental changes to unrelated code while editing?

The best way to prevent accidental changes to unrelated code is to restrict edits to a specific directory. By locking the editing boundary, you ensure that only files within the allowed folder can be modified, keeping other code safe.

When should I restrict edits to a specific directory?

You should restrict edits to a specific directory when debugging to prevent accidentally fixing unrelated code, or when you want to scope changes to a single module. Use it whenever you need to lock down edits to a specific folder.