freeze

Restrict Edit and Write operations to a defined directory boundary.

11|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill freeze-pillip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/freeze
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill freeze-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Blocks file edits outside a specified directory boundary to scope work to a module, protecting critical areas during development.

Core Features & Use Cases

  • Restricts Edit/Write operations to within the allowed boundary.
  • Supports accurate detection of repository roots, including worktrees, to prevent accidental edits.
  • Easy deactivation by removing the boundary marker at .claude-kit/freeze-dir.txt.

Quick Start

Set the allowed edit boundary by providing a directory path to freeze so only that area can be edited.

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 in a Git repository?

To restrict file edits to a specific directory, you can block edits outside a defined boundary by setting an allowed edit path. This scopes work to a module and prevents accidental changes to critical areas during development.

Can I scope edits in a Git worktree to prevent modifying files outside my module?

Yes, scoping edits in a Git worktree is supported through accurate detection of repository roots. This prevents accidental edits outside your defined boundary, ensuring work remains isolated to the correct worktree directory.

How do I set up a boundary to block write operations outside my project directory?

You set up a boundary by providing a directory path to create a boundary marker file. This file's path is resolved to an absolute path, which then enforces the block on write and edit operations outside that directory.

What is the best way to safeguard critical areas of my codebase during development?

The best way to safeguard critical areas is to block edits outside a specified directory boundary. By scoping work to a single module, you protect other parts of the repository from accidental modification.

How do I remove the edit block when I need to work outside the directory boundary?

You remove the edit block by deleting the boundary marker file located at .claude-kit/freeze-dir.txt. Removing this file deactivates the restriction, allowing edit and write operations across the entire repository again.