gs:freeze

Block edit and write operations to files outside a specified directory during a session.

34|6|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-freeze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gs:freeze
Source: https://github.com/thanh-abaii/gstack-windows-port/tree/main/skills/gstack-freeze
Command: npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-freeze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps to prevent accidental editing of files outside of a specified directory, which is beneficial for debugging and when working on specific modules or projects.

Core Features & Use Cases

  • File Edit Restriction: Blocks any edit or write operations outside the allowed directory path.
  • Session Scope: The restriction persists for the duration of the session.
  • Use Case: When you need to ensure that only certain files are edited to avoid unintended changes.

Quick Start

Run /gs:freeze and provide the path to the directory where you want to restrict edits.

Frequently Asked Questions about gs: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 for debugging?

You can restrict file edits by running the freeze command and providing the target directory path. This blocks edit and write operations to files outside that specified directory for the entire session.

How does directory protection prevent accidental changes to code modules?

Directory protection prevents accidental changes by enforcing a session scope check script before edit or write commands execute. This mechanism blocks any file modification outside the specified directory, ensuring code module isolation.

Can I limit write operations to a single project folder during a coding session?

Yes, you can limit write operations to a single project folder by initiating a session scope restriction. The constraint persists for the duration of the session, blocking any unintended file modifications outside that directory.

What is the best way to isolate code changes when working on specific modules?

The best way to isolate code changes is to restrict file edits to a specific directory. This blocks accidental write operations outside the allowed path, ensuring that only your targeted module files are modified.

How do I start a session with file edit restrictions enabled?

To start a session with file edit restrictions, execute the freeze command and provide the path to your desired directory. This input initializes the session scope and blocks modifications outside that path.