freeze

Restrict Edit and Write operations to a designated directory for the session.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/benrapport/Vote-Better --skill freeze-benrapport
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/benrapport/Vote-Better/tree/main/.claude/skills/gstack/freeze
Command: npx skills add https://github.com/benrapport/Vote-Better --skill freeze-benrapport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the session, blocking any Edit or Write outside the allowed path. Use when debugging to prevent accidentally changing unrelated code, or when you want to scope changes to one module.

Core Features & Use Cases

  • Enforce a per-session edit boundary to prevent accidental modifications outside a designated directory.
  • Prompt the user to specify the boundary (AskUserQuestion) and persist it across the session.
  • Integrate with PreToolUse hooks to block Edit and Write operations targeting files outside the boundary.

Quick Start

Provide the directory path to restrict edits to, then start a session to enforce the 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 coding session?

Restricting file edits to a specific directory involves setting a per-session boundary that blocks Edit and Write operations outside the allowed path. This enforces a strict scope for your current work.

What is a prehook edit boundary and how does it prevent accidental code changes?

A prehook edit boundary is a PreToolUse hook that intercepts Write and Edit tools before they execute. It blocks file modifications targeting paths outside a user-designated directory, preventing accidental changes.

Can I lock down a directory scope for debugging without affecting other modules?

Yes, you can lock down a directory scope for debugging by specifying an allowed path via user input. The session enforces this boundary and prevents any edits to unrelated code or modules outside that directory.

How do I start enforcing a scoped edit boundary for my current work session?

To start enforcing a scoped edit boundary, provide the target directory path when prompted via AskUserQuestion. This input sets the boundary for the session and activates the hook to block outside edits.

When should I use a per-session edit boundary for file modifications?

Use a per-session edit boundary when debugging to prevent changing unrelated code, or when you want to scope all modifications to one specific module or directory during a focused work session.