freeze

Block Edit and Write operations outside a designated directory via a PreToolUse hook.

Updated Dec 13, 2017

Search Tags:#bash #hook #freeze #pretool-use #edit-boundary #directory-restriction #development-debugging

Ready to run

npx skills add https://github.com/dogeared/tnra --skill freeze-dogeared

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/dogeared/tnra/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/dogeared/tnra --skill freeze-dogeared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict file 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

Enforces an edit boundary per session via a PreToolUse hook.
Executes a boundary check script (bin/check-freeze.sh) before Edit/Write operations.
Ideal for debugging or scoped development to prevent unintended changes.

Quick Start

Provide the directory path to restrict edits to, and subsequent Edit or Write operations outside that boundary will be blocked.

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

To restrict file edits to a specific directory, you need an edit boundary mechanism. This Skill uses a PreToolUse hook to run a boundary check script before any Edit or Write operations, blocking accidental modifications outside your designated folder.

What is a PreToolUse hook for preventing accidental code changes?▼

A PreToolUse hook for preventing accidental code changes is a script that intercepts file modification commands before they execute. It enforces a session state boundary check, ensuring edits remain scoped to a single directory to avoid fixing unrelated code.

How do I scope file writes to one folder to prevent modifying unrelated modules?▼

To scope file writes to one folder and prevent modifying unrelated modules, you apply a session-wide edit boundary. By setting a designated directory path, subsequent operations outside that boundary are automatically blocked by a pre-execution hook.

Can I use a bash hook to freeze edits when debugging code?▼

Yes, you can use a bash hook to freeze edits when debugging code. This approach stores the allowed directory in a session state and uses a boundary check script to block any Write or Edit operations outside that specific path during your debugging session.

Are there limitations to using directory-restriction hooks for scoped development?▼

A limitation of using directory-restriction hooks for scoped development is that the boundary applies per session. You must explicitly provide the directory path to restrict edits to, and the hook only blocks Edit and Write operations outside that allowed path.