freeze

Block Edit and Write operations outside a specified directory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict 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

  • Locks edits to a user-specified directory for the duration of the session.
  • Prevents accidental modifications to files outside the defined boundary during development.
  • Useful to isolate changes to a single module while debugging or reviewing code.

Quick Start

Ask the user for a directory to freeze and apply 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 debugging session?

You can restrict file edits by locking a chosen directory boundary for the current session, which blocks Edit and Write operations outside the allowed path. This prevents accidental modifications to unrelated code while debugging a scoped module.

Why do I need to lock edits to a single folder when debugging?

Locking edits to a single folder prevents accidental modifications to unrelated code while debugging. By enforcing a boundary path, you can isolate changes to one module and avoid fixing issues outside the target directory.

Can I block Write and Edit operations outside a specified module path?

Yes, you can block Write and Edit operations outside a specified module path by applying a directory freeze. A PreToolUse hook enforces the boundary and stops any file modifications outside the allowed directory.

What's the best way to scope development changes to one directory?

Scoping development changes to one directory is best achieved by freezing a boundary path for the session. This stores the allowed directory in a state file and safely resolves paths to block any edits outside that module.

Does the directory freeze tool require any dependencies to run?

The directory freeze tool requires no dependencies to run. It uses a PreToolUse hook to enforce the boundary and stores the freeze state locally, allowing you to lock edits without installing additional packages.

When should I not use a directory freeze boundary?

You should not use a directory freeze boundary when you need to make changes across multiple modules or outside the scoped path during a session. The tool blocks all Edit and Write operations outside the specified directory, limiting broader development workflows.