unfreeze

Clear the freeze boundary to allow edits across all directories.

Updated Mar 23, 2026

Search Tags:#automation #bash #session-management #state-file #gstack #edit-boundary #unfreeze

Ready to run

npx skills add https://github.com/binfen1/my-skills --skill unfreeze-binfen1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/unfreeze
Command: npx skills add https://github.com/binfen1/my-skills --skill unfreeze-binfen1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories within a session so you can continue working without restarting.

Core Features & Use Cases

Removes the active freeze constraint, widening edit scope across project directories.
Works within Claude Code workflows by reading and updating the gstack state file location.
Use case: You want to modify multiple config files after a group of changes is completed without re-freezing, so you can continue editing seamlessly.

Quick Start

Run the unfreeze skill to remove the current edit boundary and enable 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 edit boundaries and unfreeze directories in a bash session?▼

To unfreeze directories, run the unfreeze command to clear the freeze boundary set by /freeze, allowing edits across all directories within the active session. It updates the gstack bash state file to widen the edit scope.

Can I widen the edit scope during an active session without restarting?▼

Yes, you can widen the edit scope without restarting by clearing the active freeze constraint. The unfreeze command removes the edit boundary on the fly so you can continue modifying multiple project directories seamlessly.

What is a freeze boundary and when do I need to clear it?▼

A freeze boundary restricts edits to certain directories after a group of changes is completed. You need to clear it when you want to modify multiple config files or widen your edit scope across project directories without re-freezing.

Does the unfreeze command work with gstack state files and session management?▼

Yes, the unfreeze command works by reading and updating the gstack bash-based state file location. It manages session state and updates a usage log for analytics while clearing the active edit boundary.

What's the best way to continue editing multiple config files after a freeze is applied?▼

The best way to continue editing is to run the unfreeze command to remove the current edit boundary. This instantly enables edits across all directories so you can modify config files without ending the session.

Why does my session still have an edit boundary after completing changes?▼

The edit boundary persists because the freeze constraint set by /freeze remains active in the gstack state file. You need to explicitly run the unfreeze command to clear the boundary and restore full edit access.