unfreeze

Remove the /freeze edit boundary to enable edits across all directories.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill unfreeze-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/gstack/skills/unfreeze
Command: npx skills add https://github.com/xotong/claude-marketplace --skill unfreeze-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories again within the current session. 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". (gstack)

Core Features & Use Cases

  • Widen edit scope across all directories within the active gstack session.
  • Provides a safe fallback if no boundary is set, with a clear user message.
  • Integrates with session controls to maintain context until explicitly ended or re-frozen.

Quick Start

Run the unfreeze command inside an active gstack session to remove the freeze boundary and enable edits everywhere.

Frequently Asked Questions about unfreeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove an edit boundary to allow edits across all directories?

To remove an edit boundary and allow edits across all directories, run the unfreeze command within an active gstack session. It clears the boundary file set by /freeze, widening the edit scope across the repository until you re-freeze or end the session.

What happens if I unfreeze when no edit boundary is set?

If you unfreeze when no edit boundary is set, the process provides a safe fallback. It validates the existence of a boundary file, finds none, and prints a clear no-boundary message instead of throwing an error.

Does the unfreeze command require an active gstack session?

Yes, the unfreeze command is applied within an active gstack session. It relies on session controls to maintain context and widen the edit scope until the session is explicitly ended or re-frozen.

How does session management handle edit scope after unfreezing?

After unfreezing, session management maintains the widened edit scope across all directories until you explicitly end the session or re-freeze the boundary. This ensures continuous context during repository work.