freeze

Restrict file edits to a user-specified directory during coding sessions.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/binfen1/my-skills --skill freeze-binfen1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/freeze
Command: npx skills add https://github.com/binfen1/my-skills --skill freeze-binfen1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory during a session to prevent accidental or unauthorized changes outside the intended scope.

Core Features & Use Cases

  • Boundary enforcement: Only edits within the configured directory are allowed, reducing drift and mistakes.
  • Session persistence: The boundary remains active for the entire session via a lightweight state file.
  • Use Case: While debugging a module, you can lock edits to that module's folder to avoid touching unrelated code.

Quick Start

Set the freeze boundary by providing the target directory.

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 an interactive coding session?

To restrict file edits to a specific directory during an interactive coding session, you can use a boundary enforcement skill that verifies each edit path against a user-specified target folder via a shell script, preventing unauthorized changes.

Why do I need edit boundary enforcement for debugging workflows?

Edit boundary enforcement is needed for debugging workflows because it prevents accidental modifications to unrelated code by locking edits to a specific module's folder, reducing drift and mistakes while you focus on the targeted scope.

Can I lock directory edits for an entire session without reapplying the restriction?

Yes, you can lock directory edits for an entire session without reapplying the restriction, because the boundary remains active through a lightweight state file that persists your configured scope until the session ends.

Does the directory edit lock work without additional dependencies or components?

Yes, the directory edit lock works without additional dependencies or components, as it implements the boundary check entirely through a frontmatter-configured skill and a lightweight shell script to validate paths.

What is the best way to prevent accidental code changes outside a target folder?

The best way to prevent accidental code changes outside a target folder is to set a freeze boundary that enforces edit restrictions through path validation, ensuring only files within the allowed directory are modified.