freeze

Restrict file edits to a specified directory within a session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that file edits are restricted to a specified directory, preventing accidental changes to unrelated files.

Core Features & Use Cases

  • Directory Locking: Lock the editing scope to a specific directory.
  • Session Boundary: The restriction persists for the session.
  • Use Case: Ideal for debugging or when you want to ensure changes are made only within a particular code module.

Quick Start

Run the /freeze command and specify 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 a coding session?

Yes, you can restrict file edits to a specific directory by applying a session-specific lock file. This establishes a session boundary that prevents accidental changes to unrelated files within your project.

Why do I need directory locking when debugging a specific code module?

Directory locking is needed when debugging a specific code module to ensure changes are made only within that particular scope. It prevents accidental modifications to unrelated files by enforcing a strict session boundary.

How does a session boundary prevent accidental changes to unrelated files?

A session boundary prevents accidental changes to unrelated files by using a session-specific lock file to restrict text editing tools. This confines all modifications strictly to the specified directory until the session ends.

Can I lock the editing scope for text editing tools without changing my entire project configuration?

Yes, you can lock the editing scope for text editing tools without altering your project configuration by using a session-specific lock file. This restricts file edits only for the current session, leaving the broader project setup unchanged.

What are the limitations of using a session-specific lock file for directory restriction?

The limitation of using a session-specific lock file for directory restriction is that the boundary persists only for the current session. It applies solely to text editing tools, meaning other file manipulation methods may bypass the lock.