freeze

Restrict Edit and Write operations to a configured directory boundary.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/kitfunso/omniskill --skill freeze-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/kitfunso/omniskill/tree/main/skills/freeze
Command: npx skills add https://github.com/kitfunso/omniskill --skill freeze-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restrict edits to a specific directory for the session to prevent editing files outside the allowed path, helping avoid accidental changes during debugging or focused work.

Core Features & Use Cases

  • Restrict edits to one directory within a session to keep changes scoped.
  • Persist a freeze boundary in a state file and apply it to all Edit and Write operations.
  • Log boundary violations for audit and improvement of workflow discipline.

Quick Start

Configure the freeze boundary to a directory and begin editing only inside that path.

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 single directory during an active debugging session?▼

To restrict file edits, configure a freeze boundary that scopes all Edit and Write operations to a specific directory path. The boundary persists in a state file and normalizes tool_input file paths to deny any operations outside the allowed directory.

Can I prevent accidental changes to files outside my project module while developing?▼

Yes, you can prevent accidental changes by applying directory-boundary checks to your session. This mechanism normalizes paths from edit operations and blocks attempts to modify files outside your configured freeze boundary.

How does a PreToolUse hook enforce edit restrictions on file paths?▼

A PreToolUse hook enforces edit restrictions by reading tool_input to locate the file_path, normalizing the path, and comparing it against a stored freeze boundary before allowing or denying the operation.

Does restricting edits to one directory log boundary violations for audit purposes?▼

Yes, restricting edits to one directory logs boundary violations for audit and workflow discipline improvement. When an edit operation targets a file outside the freeze boundary, the denial event is recorded.

What happens to Write operations targeting paths outside the configured freeze boundary?▼

Write operations targeting paths outside the freeze boundary are denied during the active session. The system reads the file_path from tool_input, normalizes it, and blocks the operation if it falls outside the stored directory boundary.