freeze

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

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill freeze-curielmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/curielmc/beat-SPY --skill freeze-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file edits to a specific directory for the session to prevent accidental changes outside the intended scope. This is especially useful during debugging to avoid inadvertently modifying unrelated code or when you want to scope changes to a single module.

Core Features & Use Cases

  • Enforces a freeze boundary for Edit and Write operations, blocking edits outside the designated directory.
  • Applies per session so the boundary persists until explicitly reset.
  • Ideal when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits" during development.

Quick Start

Ask the user which directory to restrict edits to, then run the /freeze command to enable the boundary 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 specific directory during a coding session?

To restrict file edits during a coding session, you establish a designated boundary folder that blocks Edit and Write operations outside that directory. This prevents accidental modifications to unrelated code by confining changes to a single specified path.

Can I lock down edits to a single folder while debugging code?

Yes, you can lock down edits to a single folder while debugging. By enabling a session-boundary restriction, the system persists the designated directory and actively denies any Edit or Write operations attempted outside that specific scope.

What is the best way to prevent accidental code changes outside a project module?

The best way to prevent accidental code changes outside a project module is to scope your work using a directory freeze. This applies a boundary for the entire session, ensuring no modifications occur outside the designated folder until explicitly reset.

Does a session boundary persist across different tasks until manually reset?

Yes, a session boundary persists across different tasks until manually reset. Once you designate a directory to restrict edits to, the freeze remains active for the entire session, continuously blocking outside Write and Edit operations.

When should I not use a folder edit restriction during development?

You should not use a folder edit restriction when your development tasks require modifying files across multiple project directories. The freeze blocks all Edit and Write operations outside the designated folder, which will prevent cross-module updates.