unfreeze

Clear the /freeze edit boundary to enable edits across all directories.

37|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/DariusCorvus/iqualize --skill unfreeze-dariuscorvus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/DariusCorvus/iqualize/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/DariusCorvus/iqualize --skill unfreeze-dariuscorvus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clears the freeze boundary that restricts edits to a subset of directories, enabling edits across the entire workspace again.

Core Features & Use Cases

  • Removes the active freeze and restores full editing permissions within the project, allowing changes anywhere.
  • Useful during sessions where you need to pivot quickly, merge changes, or adjust multiple directories without restarting the session.
  • Compatible with /freeze workflows, preserving a simple toggle to re-enable restrictions when needed.

Quick Start

Run unfreeze to clear the edit boundary and enable edits 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 an edit freeze and restore full directory editing permissions in a bash workflow?

To remove an edit freeze and restore directory editing permissions, you clear the freeze boundary using a bash command that deletes the local state file. This re-enables edits across all directories in your ongoing session without requiring a restart.

When do I need to clear an edit boundary during an active development session?

You need to clear an edit boundary when your session requires widening scope, such as pivoting quickly, merging changes, or adjusting multiple directories. Removing the freeze state file restores full workspace editing permissions for collaboration.

How does tracking the freeze state file work for restricting workspace edits?

Tracking the freeze state file works by storing the active edit boundary locally. A bash command checks this file to restrict edits to a subset of directories, and removing the file clears the restriction to enable workspace-wide changes.

Can I toggle editing restrictions on and off without restarting my current workspace session?

You can toggle editing restrictions without restarting by applying or removing the freeze state file. Running the unfreeze command deletes the boundary file, restoring full editing permissions immediately within the ongoing session.

What are the limitations of using a local state file to manage edit boundaries?

The limitation of using a local state file for edit boundaries is that the unfreeze mechanism relies on simple bash file removal. It applies only to the current local session and does not manage distributed or remote editing restrictions across multiple environments.