meow:freeze

Restrict file edits and writes to a user-specified directory during a Claude session.

14|2|Updated Mar 25, 2026

Search Tags:#claude-code #freeze #pretooluse #session-memory #directory-boundary #edit-restriction

Ready to run

npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-freeze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meow:freeze
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Afreeze
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-freeze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reduces the risk of accidental or malicious edits by locking file edits to a user-specified directory during a Claude session, helping teams debug and isolate changes without affecting unrelated code.

Core Features & Use Cases

Enforces a strict directory boundary so only files inside the allowed path can be edited or written during a session.
Persists the boundary for the duration of the session, preventing drift across commands.
Prompts the user to specify the allowed directory using the AskUserQuestion flow to initialize the boundary.

Quick Start

Configure a directory boundary by prompting the user to provide a path for edits, then apply the boundary for the session.

Frequently Asked Questions about meow:freeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I restrict Claude Code edits to a specific directory?▼

You can restrict Claude Code edits to a specific directory by setting a directory boundary that denies Edit and Write tool operations outside the allowed path. This prevents accidental file modifications during your active session.

How does a PreToolUse hook enforce directory boundaries?▼

A PreToolUse hook enforces directory boundaries by intercepting Edit and Write tool calls before execution and denying operations targeting files outside the user-specified path. The allowed directory path is persisted in session memory to prevent boundary drift.

Can I isolate code changes during a Claude session for safe debugging?▼

Yes, you can isolate code changes for safe debugging by locking file edits to a user-specified directory. This prevents Claude from modifying unrelated code, helping teams debug without affecting files outside the allowed boundary.

How do I configure an allowed directory path for Claude edits?▼

You configure an allowed directory path through an AskUserQuestion workflow that prompts you to specify the folder for edits. This initializes the boundary, which is then recorded and persisted for the duration of the active session.

What are the limitations of session memory for edit restrictions?▼

Edit restrictions using session memory apply only to the active Claude session and utilize PreToolUse hooks for Edit and Write tools. The directory boundary persists across commands within that session but does not extend to other sessions.

Why restrict file writes when debugging with Claude Code?▼

Restricting file writes when debugging with Claude Code reduces the risk of accidental or malicious edits to unrelated code. By locking edits to a specific folder, you isolate changes and maintain a safe debugging environment.