freeze

Restrict file edits to a designated directory for the current session.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill freeze-vertakhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill freeze-vertakhan

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

  • Restrict edits to a single directory for the current session.
  • Enforce the boundary for Edit and Write operations via a pre-tool hook.
  • Persist the boundary in a state file and guide users to adjust it as needed.

Quick Start

Ask the user to provide a directory path to restrict edits to, then initialize the freeze boundary.

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 during debugging, you set a designated path that blocks Edit and Write operations outside that boundary for the current session. This prevents accidental modifications to unrelated code.

How does a pre-tool hook enforce a directory edit boundary?

A pre-tool hook enforces a directory edit boundary by intercepting Edit and Write operations, checking the target path against a stored absolute directory path, and returning a denial payload for any operation outside the allowed scope.

Can I lock down edits to one folder without installing dependencies?

Yes, you can lock down edits to one folder without installing dependencies. The restriction mechanism operates via a runtime state file and pre-tool hook, requiring only a user-specified directory path to initialize.

What is the best way to scope code changes to a single module?

The best way to scope code changes to a single module is to initialize a freeze boundary that persists in a state file, actively blocking any write or edit operations attempted outside that specific directory path.

Why restrict file writes when fixing bugs in a codebase?

Restricting file writes when fixing bugs prevents the accidental correction of unrelated code, ensuring debugging changes remain scoped to the designated module and maintaining a clean boundary for the current session.