unfreeze

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill unfreeze-vertakhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill unfreeze-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After restricting edits to a specific directory with /freeze, 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 - Boundary Removal: Deletes the freeze-dir.txt state file that enforces directory-scoped edit restrictions. - Status Feedback: Reports the previously frozen directory path, or confirms when no freeze boundary was set. - Use Case: You froze edits to the src/ directory for a focused refactor, finished early, and now want to edit documentation and tests without restarting the session. ## Quick Start Ask the assistant to unfreeze edits or remove the freeze boundary so all directories become editable 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 session?▼

Run the /unfreeze command to delete the freeze-dir.txt state file that enforces the restriction. 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 restricts edits to a chosen directory by writing a freeze-dir.txt state file, while /unfreeze deletes that file to restore full edit access. You can re-freeze at any time by running /freeze again.

Does unfreeze work if no freeze boundary was set?▼

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

Why are edits still blocked after running unfreeze?▼

The /freeze hooks remain registered for the session but allow everything once the state file is gone. If edits still appear blocked, verify the freeze-dir.txt file was actually deleted from the gstack data directory.