unfreeze

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

1|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ekrishgupta/gemstack --skill unfreeze-ekrishgupta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/ekrishgupta/gemstack/tree/main/unfreeze
Command: npx skills add https://github.com/ekrishgupta/gemstack --skill unfreeze-ekrishgupta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clears the edit boundary set by /freeze, allowing edits across all directories in the current session.

Core Features & Use Cases

  • Lifts the freeze boundary to restore full editing scope across the workspace.
  • Use when asked to unfreeze, unlock edits, or allow all edits during an active session.
  • Supports quick re-freeze by re-running /freeze when needed.

Quick Start

Execute /unfreeze to clear the boundary and enable edits across all directories in the current session.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I unlock edits across all directories during an active bash session?

To unlock edits across all directories, you need to clear the edit boundary set by a freeze command. This restores full editing scope across the workspace by removing the simple state file that restricts modifications.

What happens when I unfreeze the workspace edit boundary?

Unfreezing the workspace edit boundary removes the directory restriction, instantly allowing modifications across all paths in the current session. It works by checking and deleting a simple state file using standard shell utilities.

Can I re-restrict edit permissions after unlocking all directories?

Yes, you can re-restrict edit permissions by re-running the freeze command. This allows you to quickly toggle between narrowing your edit scope and allowing all edits across the workspace as needed.

Do I need any external dependencies to clear the edit boundary in bash?

No external dependencies are required to clear the edit boundary. The workflow relies entirely on standard shell utilities and a simple state file to manage and remove the directory scope restriction.

When should I widen the edit scope to all directories in my workflow?

You should widen the edit scope when you need to make changes across the entire workspace rather than a restricted area. This is useful when an ongoing session requires broader file modifications beyond the frozen boundary.