unfreeze

Remove the freeze boundary to re-enable edits across all project directories.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/abhishekmmgn/didactic-invention --skill unfreeze-abhishekmmgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/unfreeze
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill unfreeze-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)

Core Features & Use Cases

  • Clears the boundary by removing the state file and updating the user about the change.
  • Re-enables edits across all directories in the current session without restarting.
  • Use Case: When ongoing work requires unrestricted editing after a temporary freeze.

Quick Start

Run the unfreeze command to remove the current freeze boundary and restore edit access across all directories.

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 and unfreeze all directories in my session?

To unfreeze directories, you clear the enforced edit restriction by removing the state file governing the freeze boundary. This immediately re-enables unrestricted modifications across all project paths without restarting your session.

What is a freeze boundary in filesystem state management?

A freeze boundary is an enforced edit restriction within a session that prevents modifications to specific project directories. It is managed via a state file and typically applied to protect filesystem state during temporary debugging or restructuring work.

How do I re-enable edits across all project directories during debugging?

You can re-enable edits across project directories by clearing the freeze state file. This restores unrestricted filesystem access for ongoing debugging or restructuring tasks while preserving the session hooks for potential re-enforcement later.

Does clearing the freeze boundary permanently remove the session's freeze hooks?

Clearing the freeze boundary removes the current state file to unlock edits, but it preserves the session's underlying freeze hooks. This allows you to potentially re-enforce the edit restrictions and freeze the filesystem state again later.