freeze

Restricting file edits to a specific directory involves setting a boundary path that blocks all Edit and Write operations outside that folder. The freeze Skill persists this directory boundary in a state file, validating file paths against it for the entire session.

Directory boundary edit blocking prevents accidental modifications by validating file paths against a user-specified folder before allowing any changes. When a breach occurs, it returns a clear denial, ensuring edits cannot creep into code or documents outside the intended directory.

Locking writes to a single module folder while debugging is exactly what this session-scoped safety feature supports. You set the freeze directory to your module path, and all outside edits are blocked, preventing drift and unstable builds during your debugging workflow.

To unfreeze a directory and restore edit access, you remove the persisted boundary from the state file. This action lifts the session-scoped restriction, allowing Edit and Write operations to modify files outside the previously designated folder once again.

The edit blocking feature applies directly to both Edit and Write operations. It intercepts these operations, validates the target file paths against the configured directory boundary, and blocks any attempt to modify files outside that designated folder.

File changes are denied outside the configured freeze boundary because the Skill persists a directory boundary for the session. When a path validation check detects an attempted edit outside this designated folder, it returns a clear denial to prevent accidental modifications.