unfreeze

Remove the freeze-dir.txt file to clear the edit boundary across all project directories.

Updated Mar 28, 2026

Search Tags:#cli #shell #state-management #edits #gstack #unfreeze

Ready to run

npx skills add https://github.com/24601/gastack-pre-fork --skill unfreeze-24601

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/24601/gastack-pre-fork/tree/main/unfreeze
Command: npx skills add https://github.com/24601/gastack-pre-fork --skill unfreeze-24601

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the edit boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".

Core Features & Use Cases

Remove the edit restriction set by the /freeze command, enabling edits across the entire workspace.
Useful during debugging or multi-module changes when you need to edit files beyond the frozen scope.
Example: after a freeze to implement a cross-cutting fix, quickly unfreeze to apply edits everywhere.

Quick Start

Run /unfreeze to clear the freeze boundary and resume 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 the edit freeze boundary in a gstack session?▼

To remove the edit freeze boundary in a gstack session, run the command to delete the freeze-dir.txt state file. This clears the restriction and re-enables edits across all project directories without ending the session.

What does the freeze state file do in the gstack directory?▼

The freeze state file in the gstack directory enforces an edit boundary that restricts file modifications. When this file exists in the default ~/.gstack location, edits are limited to a frozen scope, preventing cross-module changes.

Can I unlock edits across all project directories without ending my current session?▼

Yes, you can unlock edits across all project directories without ending your current session. Clearing the edit boundary removes the freeze-dir.txt state flag, immediately widening the editing scope to the entire workspace for cross-module changes.

When do I need to clear the edit boundary for cross-module changes?▼

You need to clear the edit boundary for cross-module changes when a freeze is active and you must apply edits beyond the restricted scope. This is useful during debugging or when applying urgent fixes across multiple directories.

Why are my edits restricted after applying a freeze in the shell?▼

Your edits are restricted after applying a freeze because the command creates a freeze-dir.txt state file in the gstack directory. This file sets an edit boundary that blocks modifications outside the frozen scope until the file is removed.