freeze

Restrict file edits to a user-specified directory during a session.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill freeze-jesse-l-m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill freeze-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file edits to a specific directory for the session. This prevents accidental changes outside the targeted code module and helps maintain debugging isolation.

Core Features & Use Cases

  • Enforces a live boundary for edits and writes within the current session.
  • Integrates a prompt-based setup to define the allowed directory and persists it for the session.
  • Logs boundary violations to aid auditing and troubleshooting during development.

Quick Start

Set the freeze boundary to a directory you want to protect, and start restricting edits to that path.

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 bash session?▼

To restrict file edits to a specific directory during a bash session, you can set a live boundary that blocks Edit and Write operations outside the designated path while persisting the configuration for your current session.

How does directory boundary enforcement work for debugging isolation?▼

Directory boundary enforcement for debugging isolation works by reading and persisting a user-specified path, then actively blocking Edit and Write commands outside that boundary to prevent accidental changes to other code modules.

Can I log violations when restricting file writes to a target folder?▼

Yes, you can log violations when restricting file writes to a target folder. The system automatically logs boundary violations during the session to aid auditing and troubleshooting during development.

What is the best way to prevent accidental file modifications outside a code module?▼

The best way to prevent accidental file modifications outside a code module is to apply a session-scoped edit restriction that enforces a live directory boundary, ensuring all writes stay within the designated path.

Do I need to set the freeze boundary before starting module-scoped work?▼

Yes, you need to set the freeze boundary before starting module-scoped work. A prompt-based setup defines the allowed directory and persists it for the session, ensuring changes stay restricted to that path.