unfreeze

Remove the freeze boundary to restore edit rights across all directories.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill unfreeze-curielmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/curielmc/beat-SPY --skill unfreeze-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope within a session or when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".

Core Features & Use Cases

  • Restore full project-edit access across the workspace during an active Claude session.
  • Quickly respond to prompts to unfreeze or remove the freeze without restarting the session.

Quick Start

Ask Claude to unfreeze the session so edits are allowed 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 a freeze boundary to allow edits in my active session?

To remove a freeze boundary and allow edits, the system checks for a specific state file using Bash and deletes it if found. This immediately restores full edit rights across all directories within your active session.

How do I unlock edits across all directories without restarting my session?

You can unlock edits by deleting the freeze state file directly via a Bash script. This widens the edit scope across all project directories instantly, removing the need to restart your active session.

What happens when I unfreeze my session's edit scope?

When you unfreeze your session's edit scope, the system removes the freeze boundary by deleting its state file. This restores your ability to apply edits across all directories without restriction.

Do I need any dependencies to unfreeze and restore full project-edit access?

No dependencies are required to unfreeze and restore full project-edit access. The process relies entirely on a basic Bash command to locate and remove the freeze state file from your environment.

Why are my edits restricted to a freeze boundary during a session?

Edits are restricted to a freeze boundary because a previous freeze command created a state file. This file limits the edit scope, and you must remove it to restore full access across the workspace.