unfreeze

Remove edit restrictions set by the /freeze command in the gstack framework.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the issue of a frozen edit boundary on directories, enabling full edit access again.

Core Features & Use Cases

  • Edit Boundary Removal: Removes the restriction set by /freeze, allowing modifications to all directories.
  • Unfreeze Trigger: Used in response to triggers like "unfreeze edits", "unlock all directories", and "remove edit restrictions".
  • Use Case: For instance, after performing a /freeze operation, if the user needs to allow edits to all directories without ending the session, they would use /unfreeze.

Quick Start

Execute the /unfreeze command to remove the edit restrictions.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove edit restrictions from a frozen directory?

Yes, you can unlock all directories without ending your current session by running the `/unfreeze` command. It removes the edit boundary established by `/freeze`, restoring full modification permissions across the gstack framework immediately.

How does the unfreeze command work within the gstack framework?

The unfreeze command works within the gstack framework by operating solely on the state directory where freeze information is stored. It clears this state data to remove edit restrictions, requiring no external dependencies to function.

Do I need any dependencies to use the unfreeze command?

No, you do not need any dependencies to use the unfreeze command. It operates independently, directly modifying the state directory where the freeze information is stored to remove edit restrictions.

When should I use the unfreeze command instead of ending my session?

If unfreeze is not working, check if a `/freeze` command was actually executed previously. The unfreeze command operates solely on the state directory where freeze information is stored, so it only removes restrictions if that specific state data exists.