freeze

Block Edit and Write operations outside a configured directory for the session.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill freeze-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/wodeh/gstack-kimi/tree/main/freeze
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill freeze-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the session, preventing edits outside the allowed path.

Core Features & Use Cases

  • Blocks Edit and Write outside the allowed path to prevent accidental or undesired changes during debugging or scope-limited work.
  • Persist boundary for the session via a state file and enforce the boundary for Edit/Write operations via a pre-tool hook.
  • Use case: isolate changes to a module or directory to maintain focused development and avoid touching unrelated code.

Quick Start

Set a freeze boundary by specifying the directory to restrict edits to.

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

Yes, you can prevent accidental changes to unrelated code by setting a directory boundary that denies Edit and Write operations outside the configured path, maintaining focused modular development.

How does a pre-tool hook enforce a directory boundary for session edits?

The directory boundary persists for the session by saving the boundary state to a state file, ensuring the restriction remains active across multiple Edit and Write operations until the session ends.

Can I isolate code changes to a single module without affecting other directories?

Yes, you can isolate code changes to a single module by setting a freeze boundary that restricts all Edit and Write operations to a specific directory, preventing modifications to unrelated code.

What happens if I try to edit a file outside the configured freeze boundary?

If you attempt to edit a file outside the configured freeze boundary, the pre-tool hook intercepts and denies the Edit or Write operation, preventing any changes outside the allowed directory.

Does the directory edit restriction stay active across multiple tool calls in the same session?

Yes, the directory edit restriction stays active across multiple tool calls by saving the boundary state to a state file, persisting the configuration for the entire duration of the current session.