Unfreeze

What Is This?

Overview

Unfreeze is a development workflow skill designed to clear the freeze boundary previously established by the /freeze command. When a freeze boundary is active, edits are restricted to a specific set of directories or files. Unfreeze removes that restriction, restoring full edit access across all directories without requiring the developer to end or restart the current session.

This skill is part of the gstack toolset by Garry Tan and operates within AI-assisted development environments. It works in conjunction with the /freeze command to give developers precise control over which parts of a codebase are editable at any given time. The unfreeze operation is intentionally lightweight, requiring no complex configuration to execute.

The primary value of this skill lies in its ability to widen the edit scope dynamically. Rather than toggling between entirely locked and entirely open states by restarting sessions, developers can move fluidly between focused editing modes and broad editing modes within a single continuous workflow.

Who Should Use This

• Developers who use AI coding assistants and need to control which files or directories the assistant can modify during a session
• Engineers working on large codebases who apply freeze boundaries to protect stable modules while iterating on others
• Technical leads who set up constrained editing environments for code review or pair programming sessions and need to release those constraints selectively
• Developers following structured refactoring workflows where different phases require different levels of file access
• Teams using the gstack toolset who want to manage edit scope without interrupting active sessions
• Any developer who has previously invoked /freeze and needs to restore full editing capability

Why Use It

Problems It Solves

• Removes the need to end and restart a session just to expand the edit scope after a freeze boundary has been applied
• Prevents accidental edits to protected directories by providing a deliberate, explicit mechanism for restoring access rather than an automatic one
• Reduces friction in iterative development workflows where the scope of changes naturally expands as work progresses
• Eliminates confusion about which directories are currently editable by providing a clear command to reset the boundary state
• Supports cleaner session management by allowing freeze and unfreeze operations to be used as complementary tools within the same workflow

Core Highlights

• Clears the active freeze boundary set by /freeze in a single operation
• Restores edit access to all directories without ending the current session
• Works within AI-assisted development environments using Bash and Read tools
• Responds to natural language triggers such as "unfreeze," "unlock edits," "remove freeze," and "allow all edits"
• Lightweight execution with no configuration required
• Designed as a direct counterpart to the /freeze skill for symmetric workflow control
• Maintains session continuity, preserving context and history while changing edit permissions
• Part of the gstack open-source toolset, making it auditable and extensible

How to Use It

Basic Usage

To invoke the unfreeze skill within a supported environment, use the following command:

/unfreeze

You can also trigger it using natural language phrases recognized by the skill:

unfreeze
unlock edits
remove freeze
allow all edits

Specific Scenarios

Scenario 1: Expanding scope after focused editing. A developer uses /freeze to restrict edits to the src/components directory while building a new UI feature. Once that work is complete, they invoke /unfreeze to restore access to the full project, including configuration files and backend modules, before moving on to integration work.

Scenario 2: Releasing a review lock. A technical lead freezes all directories except a specific module to guide an AI assistant through a targeted code review. After the review is complete, they run /unfreeze to allow the assistant to apply broader fixes identified during the review.

Real-World Examples

## After completing focused work in a restricted directory
/freeze src/api
## ... perform edits ...
/unfreeze
## All directories are now editable again

## Using natural language in a supported chat interface
> allow all edits
## Freeze boundary cleared, full edit access restored

When to Use It

Use Cases

• After completing a focused editing phase that required a freeze boundary
• Before running a global search-and-replace or refactoring operation across the full codebase
• When transitioning from single-module development to cross-module integration work
• After a code review session where edits were intentionally restricted to a specific area
• When an AI assistant reports that a required file is outside the current edit scope
• Before ending a session to ensure no freeze boundaries carry over to the next session
• When collaborating with another developer who needs access to directories currently under a freeze boundary