unfreeze

Removes the freeze boundary state file to allow edits in all directories.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill unfreeze-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/unfreeze
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill unfreeze-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a /freeze command has restricted edits to a single directory, you need a clean way to lift that restriction without ending the session. This Skill clears the freeze boundary so edits are permitted everywhere again. ## Core Features & Use Cases - Boundary Removal: Deletes the freeze-dir.txt state file from the gstack state directory, restoring full edit access. - State Reporting: Reports the previously frozen directory path, or tells you when no freeze boundary was set. - Use Case: After finishing focused work inside one frozen directory, run /unfreeze to continue editing files across the entire repository without restarting the session. ## Quick Start Ask the assistant to unfreeze the session and allow edits to all directories again.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove a directory edit freeze in a gstack session?

Run the /unfreeze command, which deletes the freeze-dir.txt state file from the gstack state directory. Once removed, edits are allowed in all directories again without ending the session.

What is the difference between /freeze and /unfreeze?

/freeze sets a boundary restricting edits to one directory by writing a freeze-dir.txt state file, while /unfreeze deletes that file to restore edit access everywhere. They are complementary session commands.

Does unfreeze work if no freeze boundary was set?

Yes, it handles that case gracefully. If no freeze-dir.txt file exists, it simply reports that no freeze boundary was set and makes no changes.

Do I need to restart the session after running unfreeze?

No restart is needed. The /freeze hooks remain registered for the session but allow everything once the state file is gone. You can re-freeze later by running /freeze again.

Where is the freeze state file stored?

The state file lives at freeze-dir.txt inside the directory pointed to by CLAUDE_PLUGIN_DATA, defaulting to ~/.gstack when that variable is unset.