freeze

Restrict Bash and text editing tools to a specified directory for the session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that your code edits are restricted to a specific directory, preventing accidental changes to unrelated files.

Core Features & Use Cases

  • Edit Locking: Restricts all edit operations to a defined directory.
  • Session Persistence: The lock persists for the session, ensuring continuity.
  • Use Case: When working on a complex module and want to prevent accidental edits to other parts of the codebase.

Quick Start

Set the freeze boundary to the 'src' directory by running /freeze /src.

Frequently Asked Questions about freeze

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

FAQPage Schema
How do I restrict file editing to a specific directory and prevent accidental changes?

To restrict file editing, you can lock the editing scope to a specific directory for the session, preventing any modifications to files outside that boundary.

Can I lock my code editing session to a single folder?

Yes, you can lock your code editing session to a single folder by setting a directory boundary, which persists for the entire session to ensure continuity.

Does the directory edit lock apply to bash commands and text editing tools?

Yes, the directory edit lock applies directly to both bash commands and text editing tools, ensuring that no file modifications happen outside the restricted scope.

What is the best way to protect files from accidental edits while working on a complex module?

The best way to protect files is to set an edit lock on a specific directory, which prevents accidental changes to unrelated parts of the codebase during complex module development.

How do I start a directory lock for my codebase?

You start a directory lock by running the freeze command with your target path, such as `/freeze /src`, to immediately restrict all edit operations to that directory.