unfreeze

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

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill unfreeze-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/westkite1201/garden-engine --skill unfreeze-westkite1201

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 allowed 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 for a focused refactor, finished early, and now want to make changes elsewhere in the repo without restarting the session. ## 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 freeze in Claude Code?

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

What is the difference between /freeze and /unfreeze?

/freeze sets a boundary restricting edits to a chosen directory by writing a state file, while /unfreeze deletes that state file to restore full edit access. They are complementary commands for controlling edit scope within a session.

Does unfreeze work if no freeze was set?

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

Do freeze hooks keep running after unfreeze?

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