freeze

Block file edits outside a user-specified directory during development sessions.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/SeaLion-hub/DICEE --skill freeze-sealion-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freeze
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/freeze
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill freeze-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3.

What problem does it solve?

Restrict file edits to a specific directory for the session, preventing accidental changes outside the target path during debugging or scoped development tasks.

Core Features & Use Cases

  • Blocks Edit and Write operations outside the configured boundary to keep changes contained.
  • Persists a per-session freeze boundary and enforces it across edits, helping you focus on a single module or folder.
  • Useful when you want to ensure that only a designated directory is modified, reducing accidental regressions during debugging.

Quick Start

Provide a directory path to restrict edits to; the skill will enforce the boundary for the session.

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 debugging?

Restrict file edits to a specific directory by setting a runtime boundary that checks file paths and blocks modifications outside the allowed folder. This prevents unintended changes to other modules during scoped development sessions.

What is a file edit boundary and when do I need it for workflow tooling?

A file edit boundary is a session constraint that blocks write operations outside a designated folder. You need it during debugging to prevent accidental modifications to unrelated code modules and reduce unintended regressions.

How do I lock edits to a single folder for a scoped development session?

Lock edits to a single folder by providing the directory path to establish a freeze boundary. The tool records the allowed path and denies any edit or write operations targeting files outside that configured directory.

Do I need Python 3 to enforce filesystem boundaries for code edits?

Yes, Python 3 is required to enforce filesystem boundaries for code edits. The tool uses Python to record the allowed path, check tool input file paths, and return a denial when modifications fall outside the boundary.

What happens if a tool tries to modify a file path outside the freeze boundary?

When a tool attempts to modify a file outside the freeze boundary, the system checks the file path against the allowed directory and returns a denial. This blocks edit and write operations to prevent unintended changes during debugging.