freeze

Restrict file edits to a designated directory using a JSON config and script hook.

4|1|Updated May 31, 2015
One-click install
npx skills add https://github.com/samcdavid/dotfiles --skill freeze-samcdavid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/freeze
Command: npx skills add https://github.com/samcdavid/dotfiles --skill freeze-samcdavid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Block edits outside a specified directory to prevent accidental changes during debugging or investigation.

Core Features & Use Cases

  • Restricts edits to a single directory to guard code during investigation.
  • Works with "Edit" and "Write" tools, enforcing the restriction in real-time.

Quick Start

Invoke the skill with a target directory path to freeze edits, for example /freeze /path/to/dir.

Frequently Asked Questions about freeze

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

FAQPage Schema
How do I prevent accidental file edits outside a specific directory during debugging?

You can prevent accidental file edits outside a specific directory by enforcing a real-time lock that restricts changes to a designated path during debugging or investigation sessions.

How do I lock edits to a single directory to safeguard my code?

To lock edits to a single directory, invoke the skill with the target directory path. It enforces the restriction in real-time using a configurable JSON config and a script hook.

Does the directory edit lock work with standard file modification tools?

Yes, the directory edit lock works with standard "Edit" and "Write" tools, enforcing the configured restriction in real-time across tools that modify files.

What is the best way to contain code changes during an investigation?

The best way to contain code changes during an investigation is implementing a configurable restriction via a JSON config and a script hook to block edits outside your designated directory.

Why do I need a real-time lock for restricting edits during a debugging session?

You need a real-time lock for restricting edits during debugging because it actively prevents accidental changes to files outside your target directory the moment a modification is attempted.