unfreeze

Delete the freeze-dir.txt state file to allow edits across all directories.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill unfreeze-shaythegay13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/shaythegay13/serenity-pocket-app-final/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill unfreeze-shaythegay13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the edit restrictions by removing the freeze boundary, allowing edits to resume across all directories in the workspace.

Core Features & Use Cases

  • Remove the previously set freeze boundary to permit edits everywhere within the current session.
  • Use case: you need to widen the scope of changes after a /freeze event to fix multiple configurations.
  • This Skill is applicable whenever you want to edit numerous directories without restarting the session.

Quick Start

Unfreeze the current session to allow edits across all project directories.

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 freeze and enable edits across the workspace?

To remove a directory freeze and enable edits, the system checks for a state file at STATE_DIR/freeze-dir.txt and deletes it if present. This action clears the edit restriction boundary, allowing modifications across all directories in the current session.

What is the freeze boundary in a shell workspace state?

The freeze boundary in a shell workspace state is an edit restriction mechanism. It limits modifications to a specific directory scope by creating a state file, preventing edits across other directories within the active session.

When do I need to remove edit restrictions across multiple directories?

You need to remove edit restrictions across multiple directories when widening the scope of changes after a freeze event. This is required to fix configurations or edit numerous directories without restarting the current shell session.

Do I need to restart the session to unfreeze directories?

No, you do not need to restart the session to unfreeze directories. The process deletes the freeze state file directly, immediately allowing edits across all project directories within the currently active workspace session.

Can I use the unfreeze command to edit multiple project configurations at once?

Yes, you can use the unfreeze command to edit multiple project configurations at once. By deleting the freeze boundary file, it permits edits everywhere within the current session, enabling modifications across numerous directories simultaneously.