freeze

Restrict file edits to a designated directory via a PreToolUse hook.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill freeze-txema-puch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/txema-puch/drone-ai-saturdays/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill freeze-txema-puch

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. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits".

Core Features & Use Cases

  • Enforces a per-session edit boundary by filtering tool inputs to a configured directory.
  • Integrates with PreToolUse hooks to block unauthorized edits and log boundary violations.
  • Real-world scenario: during a debugging sprint, the team freezes changes to the working module to avoid unintended drift while fixing a bug.

Quick Start

Ask the user which directory to restrict edits to, then activate the boundary so only edits within that path are allowed.

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

To restrict file edits to a specific directory, you can enforce a per-session edit boundary that blocks Edit and Write operations outside the allowed path. This prevents accidental code changes while debugging.

Can I lock down edits to a single folder to prevent code drift across a project?

Yes, locking down edits to a single folder prevents code drift across a project. It filters tool inputs to a configured directory, ensuring changes remain confined to your working module.

How does a PreToolUse hook block unauthorized file modifications?

A PreToolUse hook blocks unauthorized file modifications by reading the stored boundary path, comparing the target file_path, and denying edits that fall outside the designated directory boundary.

What is the best way to scope changes to one module when collaborating on code?

Scoping changes to one module during collaboration is best achieved by activating an edit boundary. This restricts modifications to a designated directory, preventing unintended drift while fixing bugs.

Are there limitations to restricting bash edits to a configured directory?

Limitations include that the restriction is per-session and relies on stored state. It filters tool inputs to a configured directory, meaning edits outside this boundary are denied, but the boundary itself must be set correctly beforehand.