freeze

Block Edit and Write operations outside a designated directory during a session.

Updated Apr 6, 2025
One-click install
npx skills add https://github.com/yolopunk/jedi --skill freeze-yolopunk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/yolopunk/jedi/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/yolopunk/jedi --skill freeze-yolopunk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the session to prevent accidental changes outside the intended scope.

Core Features & Use Cases

  • Interactive boundary setup: ask the user for the directory to freeze, then persist the boundary for the session.
  • Boundary enforcement: Edit and Write operations outside the allowed path are blocked via a PreToolUse hook.
  • Safe debugging and scoped changes: ideal when debugging or working on a single module to avoid unintended edits.

Quick Start

Set a boundary by providing a directory path, then edits will be allowed only within that directory 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 a debugging session?

To restrict file edits to a single directory during a debugging session, you can freeze a designated path using a persistent state file. This enforces a boundary that blocks Edit and Write operations outside the allowed directory.

What is a PreToolUse hook for directory boundary enforcement?

A PreToolUse hook for directory boundary enforcement intercepts Edit and Write operations, comparing the target file_path against a stored boundary. It denies violations before the tool executes, preventing accidental changes outside the intended module scope.

Can I block Write operations outside a specific module scope?

Yes, you can block Write operations outside a specific module scope by setting an interactive boundary. Once persisted, any Write or Edit operation targeting a file_path outside the designated directory will be automatically denied during the session.

How do I set up scoped changes to prevent accidental edits in other directories?

To set up scoped changes and prevent accidental edits, provide a directory path to freeze at the start of your session. The boundary is then persisted, ensuring all subsequent modifications remain confined to that specific directory.

Does session security boundary enforcement work for both Edit and Write operations?

Session security boundary enforcement works for both Edit and Write operations by applying a PreToolUse hook. This hook evaluates the target file_path against the frozen directory and blocks any attempts to modify files outside the designated boundary.

When should I not use directory freeze for edit control?

You should not use directory freeze for edit control when you need to make cross-module modifications or update shared configuration files outside the designated directory, as the boundary will strictly deny those Edit and Write operations.