freeze

Restrict file edits to a specified directory during a session.

9|3|Updated Jan 29, 2022
One-click install
npx skills add https://github.com/I194/PMTools_2.0 --skill freeze-i194
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill freeze-i194

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module.

Core Features & Use Cases

  • Boundary enforcement for edits within a specified directory during a session.
  • Setup prompts the user to specify the allowed directory and persists the boundary.
  • Lightweight analytics of usage, with clear guidance on how to deactivate.

Quick Start

Specify the directory to freeze, then continue your session with edits restricted 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 coding session?

You restrict file edits by setting a directory edit boundary that blocks Edit and Write operations outside an allowed folder path. This prevents accidental modifications to unrelated code during your session.

What is a directory edit boundary and when do I need it?

A directory edit boundary is a session safeguard that restricts file modifications to a single specified folder. You need it when debugging or scoping changes to one module to prevent accidentally fixing unrelated code.

How do I configure a freeze boundary for my project directory?

You configure the freeze boundary by specifying the allowed directory during the setup prompt, which persists the configuration. Runtime enforcement is then handled automatically via the check-freeze.sh hook.

Can I apply directory freeze safeguards to any coding or debugging task?

Yes, you can apply directory freeze safeguards to any coding or debugging task where edits must stay within a specified boundary. This ensures file modifications remain scoped to your target module.

How do I deactivate the session edit boundary when I no longer need it?

To deactivate the session edit boundary, you can follow the clear guidance provided by the lightweight analytics logging. This removes the directory restrictions when your scoped work is complete.