unfreeze

Remove the freeze boundary to allow edits across all directories in a gstack session.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill unfreeze-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/wodeh/gstack-kimi/tree/main/unfreeze
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill unfreeze-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session.

Core Features & Use Cases

  • Removes the freeze boundary in an active gstack session, enabling edits across the entire workspace.
  • Supports ongoing exploration or debugging without restarting the session.
  • Use Case: When you need to modify files across multiple repositories in a single session.

Quick Start

Run the unfreeze command to lift the edit restrictions and allow 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 edit boundaries in a gstack session to modify multiple directories?

To remove the edit boundary in a gstack session, run the unfreeze command. It deletes the stored freeze marker, lifting directory restrictions so you can modify files across the entire workspace without restarting.

Why does my gstack session restrict edits to a single directory?

Your gstack session restricts edits because a freeze boundary was previously set. This boundary limits modifications to a specific scope, requiring you to clear the freeze marker to allow edits everywhere.

Can I expand my edit scope across multiple repositories without ending an active session?

Yes, you can expand your edit scope without ending an active session. By clearing the freeze boundary, the unfreeze command enables ongoing exploration and debugging across multiple repositories without a restart.

What is the best way to lift directory restrictions during workflow control in gstack?

The best way to lift directory restrictions during workflow control is to run the unfreeze command. It detects the stored freeze marker, deletes it, and confirms that edits are now allowed everywhere in your workspace.

Does unfreezing a session affect my ongoing exploration or debugging workflow?

Unfreezing a session positively affects your workflow by enabling edits across the entire workspace. It supports ongoing exploration or debugging by removing directory restrictions without requiring a session restart.