unfreeze

Remove the edit restriction by deleting freeze-dir.txt from the mzstack state directory.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill unfreeze-ulanxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/Ulanxx/mzstack/tree/main/unfreeze
Command: npx skills add https://github.com/Ulanxx/mzstack --skill unfreeze-ulanxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the edit boundary that freezes directories during a session, enabling edits across the entire project again.

Core Features & Use Cases

  • Removes the edit restriction set by /freeze, allowing edits in every directory.
  • Useful for rapid experimentation, debugging, and exploratory changes without restarting the session.

Quick Start

Run the /unfreeze command to lift the boundary and allow edits across all directories.

Frequently Asked Questions about unfreeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove directory edit restrictions during an mzstack session?

Run the /unfreeze command to remove directory edit restrictions during an mzstack session. It lifts the boundary set by /freeze by deleting the freeze-dir.txt file in the state directory, enabling unrestricted edits across the entire project.

Why does the freeze state prevent me from editing files in certain directories?

The freeze state restricts edits because a /freeze command previously set a boundary file in the mzstack state directory. This locks certain directories to prevent modifications until the boundary is explicitly removed by deleting the freeze-dir.txt file.

Can I lift the edit boundary for debugging without restarting my session?

Yes, you can lift the edit boundary for debugging without restarting your session. Applying /unfreeze immediately removes the directory restriction, enabling rapid experimentation and exploratory changes across the project without interrupting the active session.

What is the best way to allow rapid edits across the entire project again?

The best way to allow rapid edits across the entire project again is to apply the /unfreeze command. It clears the edit boundary by deleting the freeze-dir.txt file in the mzstack state directory, restoring unrestricted modification access to all directories.

Does the unfreeze command require any dependencies to clear the session freeze?

No, the unfreeze command requires no dependencies to clear the session freeze. It operates independently to detect and remove the freeze state by directly deleting the freeze-dir.txt file in the mzstack state directory.