unfreeze

Remove the active freeze boundary to allow edits across all directories.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/deveshkumars/Intentra --skill unfreeze-deveshkumars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/deveshkumars/Intentra/tree/main/unfreeze
Command: npx skills add https://github.com/deveshkumars/Intentra --skill unfreeze-deveshkumars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unfreeze the editing scope by removing the restriction set by /freeze, enabling edits across all directories again.

Core Features & Use Cases

  • Lifts the freeze boundary to allow edits in all directories.
  • Re-enables full workspace collaboration without ending the session.
  • Works within an active Claude Code session and preserves /freeze hooks for easy re-freeze.

Quick Start

Ask Claude to unfreeze to clear the editing boundary and enable edits across the entire workspace.

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 and resume edits in my bash workspace?▼

To remove a freeze boundary and resume edits, the system detects the stored freeze state, deletes the boundary marker, and restores full workspace editing access within the current session.

What is a freeze boundary in workspace management?▼

A freeze boundary is an edit control restriction set by a previous /freeze command that limits editing capabilities to specific directories within an active bash session.

Can I re-enable full workspace access without ending my current session?▼

Yes, you can re-enable full workspace access without ending the session by clearing the active freeze boundary, which lifts directory restrictions while preserving hooks for easy re-freezing.

Does removing the editing restriction delete the /freeze hooks?▼

No, removing the editing restriction does not delete the /freeze hooks; it only clears the current boundary marker, allowing you to easily re-freeze the workspace later.

What happens if I try to edit when a freeze boundary is active?▼

When a freeze boundary is active, editing is restricted across directories; you must clear the stored freeze state to delete the boundary marker and restore unrestricted editing.

When should I not use the unfreeze command?▼

You should not clear the freeze boundary if you need to maintain strict edit control over directories for safety or compliance, as it restores unrestricted editing across the entire workspace.