freeze

Block file edits outside a designated directory during debugging sessions.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill freeze-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/freeze
Command: npx skills add https://github.com/yckkkk/reo --skill freeze-yckkkk

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". (gstack)

Core Features & Use Cases

  • Freeze edits to a directory to lock editing scope and prevent accidental changes across modules.
  • Enforce a boundary during debugging sessions to isolate changes to a target folder.
  • PreToolUse integration via check-freeze.sh to validate edits against the boundary.

Quick Start

Ask the user which directory should be restricted for edits, then save that path and start enforcing the boundary.

Frequently Asked Questions about freeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lock file edits to a specific directory during debugging?

To lock file edits to a specific directory, you can freeze changes by setting a designated folder as an editing boundary. This blocks Write and Edit operations outside the allowed path, preventing accidental drift across modules.

Can I restrict code modifications to a single module to prevent drift?

Yes, you can restrict code modifications to a single module by enforcing a scoped editing boundary. This ensures only the target folder remains modifiable while blocking changes to unrelated code during active sessions.

How does a PreToolUse hook validate file paths against a stored boundary?

A PreToolUse hook validates file paths by checking the requested file_path against a boundary stored in a state file. If the path falls outside the designated directory, the edit operation is blocked before execution.

What is the best way to scope changes to one folder when fixing bugs?

The best way to scope changes to one folder when fixing bugs is to freeze edits to that target directory. This isolates modifications, ensuring you do not accidentally fix or alter unrelated code outside the boundary.

Does restricting edits to a designated path work across different tools?

Yes, restricting edits to a designated path works across tools by enforcing a scoped editing boundary through a PreToolUse hook. This validates all file paths against the stored boundary, regardless of the tool attempting the edit.

What happens if I try to edit a file outside the frozen directory boundary?

If you try to edit a file outside the frozen directory boundary, the PreToolUse hook blocks the operation. The validation check compares the file path against the persisted state file and prevents any Write or Edit action outside the scope.