unfreeze

Clear the stored freeze boundary to resume directory edits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary that restricts edits, enabling edits across all directories again.

Core Features & Use Cases

  • Clear the freeze boundary to resume broad editing rights in a project workspace.
  • Applicable in development sessions where a user needs to widen editing scope after a temporary lock or pause.

Quick Start

Run the unfreeze command to clear the freeze boundary and restore full edit access.

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 restriction in my shell workspace?

To remove a directory edit restriction, you need to clear the stored freeze boundary. This deletes the state file locking your workspace, enabling edits across all directories again.

What is a freeze boundary in a development session?

A freeze boundary is a temporary edit restriction applied to a project workspace. It stores a state file that limits editing scope until explicitly cleared to resume broad editing rights.

How do I resume broad directory edits after a temporary lock?

To resume broad directory edits after a temporary lock, run the unfreeze command. It checks for the state file, deletes it if present, and restores full edit access across all directories.

Can I widen my editing scope in a bash session without manual file deletion?

Yes, you can widen your editing scope by running a shell-based command that checks for the freeze boundary state file. It automatically deletes the file if present and informs you of the outcome.

What happens if I run the unfreeze command when no freeze boundary is active?

If no freeze boundary is active, the shell-based check finds no state file to delete. The command simply informs you of the outcome without making changes to your workspace.