unfreeze

Remove the /freeze edit scope restriction while preserving freeze hooks.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/a29paul/hexlens --skill unfreeze-a29paul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/a29paul/hexlens --skill unfreeze-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When using the /freeze command to restrict edits to specific directories during a development session, you cannot modify files outside the allowed scope without ending the session. This Skill eliminates that limitation by clearing the freeze boundary, letting you edit any directory again while keeping your current session active.

Core Features & Use Cases

  • Instant Freeze Removal: Clears the edit restriction set by /freeze in one step.
  • Session Preservation: Retains registered freeze hooks for the rest of the session, so you can re-enable the freeze later if needed.
  • Use Case: You froze edits to only the src/ directory while working on a feature bugfix, but need to quickly update a README file in the repo root. Run this Skill to temporarily access all directories without losing your freeze configuration.

Quick Start

Use the unfreeze skill to clear the current edit freeze and allow modifications to all directories in your project.

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 from a frozen directory in a gstack development session?

To remove edit restrictions from a frozen directory in a gstack development session, use the unfreeze command to clear the freeze boundary. This restores full directory edit permissions, allowing you to modify files outside the originally allowed scope without terminating your current workflow.

Can I temporarily edit files outside the allowed directory scope without ending my session?

Yes, you can temporarily edit files outside the allowed directory scope without ending your session. By removing the edit freeze, you restore full directory access while keeping your current development workflow active and preserving pre-registered freeze hooks for later use.

Does removing an edit freeze delete the session's freeze configuration?

Removing an edit freeze does not delete the session's freeze configuration. The process clears the current edit boundary but retains pre-registered freeze hooks, allowing you to re-enable the directory restrictions later in the same development session if needed.

When do I need to clear a freeze boundary during a coding workflow?

You need to clear a freeze boundary during a coding workflow when a restricted edit scope prevents necessary modifications. For example, if edits were frozen to the src/ directory but you must update a root README file, clearing the boundary grants immediate access to all project directories.