freeze

Restrict Edit and Write operations to a designated directory per session.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/jayzalowitz/skytwin --skill freeze-jayzalowitz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/jayzalowitz/skytwin/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/jayzalowitz/skytwin --skill freeze-jayzalowitz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a single directory for the current session to prevent accidental changes elsewhere.

Core Features & Use Cases

  • Enforces Edit and Write boundaries to a chosen folder.
  • Works per session and persists during a development task, debugging, or experiments.
  • Useful when you want to isolate changes to one module or directory for safer testing.

Quick Start

Set the freeze boundary to a directory to restrict edits within that path for the current session.

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 single directory during an active development session?

You can restrict file edits to a single directory by setting a persistent boundary that enforces Write and Edit restrictions, confining all changes to that specific folder for the duration of your session.

What is the best way to prevent accidental code changes outside a specific module while debugging?

Preventing accidental code changes outside a specific module requires setting an edit boundary that blocks Write operations beyond your designated directory, reporting violations to guide corrective actions.

Can I confine bash session edits to one folder for safer testing?

Yes, you can confine bash session edits to one folder by applying a persistent edit boundary that resolves paths and enforces restrictions, isolating changes for safer testing.

Does the directory protection boundary persist across different tasks in the same session?

The directory protection boundary persists across active development tasks, debugging, and experiments within the same session, maintaining directory protection until the session ends.

What happens when a write operation violates the directory edit boundary?

When a write operation violates the directory edit boundary, the system blocks the action and reports the violation, guiding you to correct the path and keep changes within the designated folder.

When should I not use a session edit boundary for directory protection?

You should not use a session edit boundary when your development task requires modifying shared modules or files outside a single designated directory, as the restrictions will block necessary changes.