unfreeze

Remove the freeze marker to permit edits across all directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the edit boundary set by /freeze, allowing edits to all directories in the session.

Core Features & Use Cases

  • Remove the freeze boundary to restore unrestricted edits across the project.
  • Works in active sessions where a user needs to resume development after a temporary restriction.
  • Use in tandem with /freeze to toggle controlled editing windows as needed.

Quick Start

Run the unfreeze command to clear the boundary.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove a directory edit freeze and resume unrestricted file edits in a bash session?

To remove an edit freeze and resume unrestricted edits, you need to clear the session's freeze boundary marker. This action reverts the active session state to permit direct modifications across all project directories again.

What is a freeze boundary in a CLI session and when should I clear it?

A freeze boundary is a temporary edit restriction set across project directories to prevent unintended modifications. You should clear this state when you need to resume active development and want to restore unrestricted file editing capabilities.

How do I toggle controlled editing windows in my project session?

You can toggle controlled editing windows by using a freeze command to set the boundary and an unfreeze command to clear it. This permits toggling between restricted and unrestricted edit states as needed during development.

Do I need any special dependencies to clear an edit boundary in my bash session?

No special dependencies are required to clear an edit boundary. The process checks the active session for a freeze state marker and removes it directly within the CLI environment to restore edit permissions.

Why are my file edits still restricted after attempting to unfreeze the project directory?

If edits remain restricted, the session may not have detected a valid freeze state marker to remove, or the boundary was already cleared. The command checks for the marker's presence and informs you of the current result.