freeze

Restrict file edit operations to a user-defined directory.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill freeze-santiagoisper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA/tree/main/.agents/skills/gstack/freeze
Command: npx skills add https://github.com/Santiagoisper/BOPE_VERSION_DEFINITIVA --skill freeze-santiagoisper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that file edits are confined to a specified directory, preventing unintended changes to other parts of the file system.

Core Features & Use Cases

  • Edit Restriction: Blocks 'Edit' and 'Write' operations outside the allowed directory.
  • Use Case: Ideal for debugging sessions or when changes should be isolated to a single module.

Quick Start

To activate the edit restriction, run /freeze <path>, where <path> is 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 an active coding session?

To restrict file edits to a specific directory during a session, you can use a directory lock mechanism that blocks 'Edit' and 'Write' operations outside the user-defined path. This confines changes to the target folder.

What is directory edit restriction used for in software engineering?

Directory edit restriction is used to isolate changes to a single module or directory, preventing unintended modifications to other parts of the file system. It is ideal for controlled debugging sessions where boundaries must be enforced.

How do I lock a directory path to prevent unintended file modifications?

Lock a directory path by running the `/freeze` command followed by your target directory path. This enforces edit restrictions based on the user-defined boundaries for the current session.

Does edit restriction block both writing and editing files outside the allowed directory?

Edit restriction blocks both 'Edit' and 'Write' operations outside the allowed directory. It limits file edit operations to the designated target path to prevent unintended changes elsewhere in the file system.

Can I use directory lock to isolate changes for a single module during debugging?

You can use a directory lock to isolate changes for a single module during debugging. By confining edits to a specified directory, it prevents unintended modifications to other parts of the file system.

When should I not rely on session control for file edit restrictions?

Do not rely on session control for file edit restrictions if you need persistent lock rules that remain active after the session ends. This mechanism only enforces edit boundaries during the active session runtime.