Verified:GitHub

unfreeze

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

Updated Mar 23, 2026

Search Tags:#bash #workflow control #session state #unfreeze #directory restriction #edit permissions

One-click install

npx skills add https://github.com/dhnpmp-tech/project-agent --skill unfreeze-dhnpmp-tech

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill unfreeze-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After using /freeze to restrict edits to a specific directory, you may need to widen the edit scope without ending the session. This Skill removes that restriction so edits are permitted everywhere again. ## Core Features & Use Cases - Clear Freeze Boundary: Deletes the freeze-dir.txt state file that enforces directory-scoped edit restrictions. - Session-Safe Operation: Works within the current session; freeze hooks remain registered but allow everything once the state file is gone. - Use Case: You froze edits to the src/ directory while refactoring, finished the task, and now want to update documentation in docs/ without restarting the session. Run /unfreeze to restore full edit access. ## Quick Start Ask the assistant to unfreeze 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 restriction in my 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 commands?▼

The /freeze command sets a boundary restricting edits to a chosen directory by writing a state file. The /unfreeze command deletes that state file, widening the edit scope back to all directories.

Does unfreeze work if no freeze boundary was set?▼

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

Do freeze hooks stop working after running unfreeze?▼

No, the freeze hooks remain registered for the session but allow all edits because the state file no longer exists. To re-enable restrictions, run /freeze again.