freeze

Block Edit and Write operations outside a user-specified directory.

Updated Mar 19, 2026

Search Tags:#bash #freeze #dev-workflow #edit-blocker #prehook #directory-boundary

Ready to run

npx skills add https://github.com/onlypfachi/chief --skill freeze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/onlypfachi/chief/tree/main/freeze
Command: npx skills add https://github.com/onlypfachi/chief --skill freeze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental or intentional edits outside a defined directory during debugging or scoped development, helping you keep changes contained.

Core Features & Use Cases

Scope edits to a single module by setting a boundary directory.
Block edits and writes outside the allowed path for the duration of the session.
Works with Edit and Write operations, integrating with PreToolUse hooks to enforce the boundary.

Quick Start

Provide a directory path to restrict edits to, and the system will block any Edit or Write outside that boundary.

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 bash development session?▼

By setting a directory boundary, you block Edit and Write operations outside that path for the session duration. This restricts file edits to a single directory and prevents accidental modifications elsewhere in your project.

What is the best way to prevent accidental file writes outside a project module?▼

Enforcing a runtime boundary via a PreToolUse hook prevents accidental file writes by checking file paths against your allowed directory. Edit and Write operations targeting files outside the boundary are blocked before execution.

Can I scope changes to a single directory using a prehook in my dev workflow?▼

Yes, you can scope changes to a single directory by configuring a prehook in your dev workflow. The prehook validates file paths against a boundary and blocks any edit or write attempts targeting files outside that directory.

Does the edit blocker work with both Edit and Write operations?▼

Yes, the edit blocker works with both Edit and Write operations. It integrates with PreToolUse hooks to intercept and check file paths before any modification occurs, ensuring changes remain within the directory boundary.

Why are my edits being blocked outside my debugging scope?▼

Your edits are being blocked because a directory boundary is active, enforcing a runtime check via a state file. The PreToolUse hook intercepts your edit operations and prevents any file modifications outside the specified boundary path.