freeze

Restricts file edits and writes to a specified directory via bookmarking.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/smarmen86/claude-code-kit --skill freeze-smarmen86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/smarmen86/claude-code-kit/tree/main/skills/freeze
Command: npx skills add https://github.com/smarmen86/claude-code-kit --skill freeze-smarmen86

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill prevents accidental modifications to files outside of a designated project scope, ensuring that edits remain contained within a specific directory during a session.

Core Features & Use Cases

  • Boundary Enforcement: Automatically blocks any Edit or Write operations that target files outside the user-defined path.
  • Session Persistence: Maintains the restricted scope throughout the conversation until explicitly removed or the session ends.
  • Use Case: When working on a large monorepo, use this skill to lock edits to a specific microservice folder to prevent the AI from inadvertently modifying shared configuration files or unrelated modules.

Quick Start

Invoke the freeze skill and provide the absolute path to the directory you wish to restrict all future file 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 a development session?

To restrict file edits to a specific directory, you apply directory boundary enforcement that validates file paths against a defined root before executing write operations. This prevents accidental modifications to out-of-scope files.

What is scope control in file system editing and why is it needed?

Scope control in file system editing limits write operations to a user-defined boundary, preventing accidental modifications to unrelated files. It is needed when working in large monorepos to stop AI from inadvertently changing shared configuration files or unrelated modules.

How do I lock AI write operations to a specific microservice folder in a monorepo?

You lock AI write operations to a microservice folder by invoking a restriction mechanism with the absolute path to that directory. This establishes session-based state tracking to validate all future file edits against the defined root.

Does the directory boundary restriction persist throughout the entire conversation?

Yes, the directory boundary restriction maintains the limited scope throughout the entire conversation. The session persistence ensures edits remain contained within the specific directory until explicitly removed or the session ends.

Can I use file system guardrails to prevent modifications to shared configuration files?

Yes, you can use file system guardrails to prevent modifications to shared configuration files by automatically blocking any edit or write operations that target paths outside your user-defined directory boundary.