freeze

Block file edits outside a specified directory during a session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The 'freeze' skill addresses the problem of accidentally editing files outside of a desired directory during development or debugging sessions.

Core Features & Use Cases

  • Selective File Locking: Allows the user to specify a directory and lock editing to it, blocking any attempts to edit files outside this directory.
  • Session-based Lock: The lock persists for the duration of the session, providing a safe environment for focused work.
  • Use Case: Useful for debugging or developing within a specific project directory while preventing unintentional changes to unrelated files.

Quick Start

Run the /freeze command to lock file edits to a specific directory. You will be prompted to enter the directory path you want to restrict edits to.

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 an active development session?

To restrict file edits to a specific directory during a development session, you can apply a session-based lock that checks file paths and blocks any text or bash editing operations outside the allowed boundary.

What is the best way to prevent accidental modifications to files outside of my project directory?

Preventing accidental modifications to files outside your project directory requires a selective file locking mechanism that enforces edit restrictions by validating paths before any bash or text editing command executes.

Can I lock down directory protection so it only blocks bash and text editing commands?

Yes, directory protection locks can specifically target bash and text editing commands, intercepting the operations to check the target path and blocking the execution if the file resides outside the permitted directory.

How does session management for file locking work when debugging focused code?

Session management for file locking works by applying a persistent edit restriction boundary for the duration of your session, ensuring debugging remains safely contained within a specified directory.

Does file locking for edit restriction persist automatically until I end my session?

Yes, session-based file locking persists automatically for the duration of the entire session, continuously enforcing directory protection and preventing any edits to files outside the allowed path until the session concludes.

When should I not use a session-based edit restriction for directory protection?

You should not use a session-based edit restriction when you need to frequently modify files across multiple unrelated directories, as the lock will continuously block bash and text editing operations outside the single allowed path.