unfreeze

Remove the freeze boundary on directories to allow edits across the workspace.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill unfreeze-jeremiahellington
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/unfreeze
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill unfreeze-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Clear the boundary between frozen and editable areas to resume comprehensive edits.
  • Supports continuing sessions without restarting tools or losing context.
  • Real-world use: after a freeze, you need to fix a bug across multiple modules quickly.

Quick Start

Use unfreeze to remove the edit boundary and allow 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 an edit freeze on directories in my workspace?

To remove an edit freeze on directories, you can use an unfreeze command that clears the boundary set by a prior freeze. It restores full edit access across all project folders without requiring a session restart.

Why does my workspace still have frozen directories when I try to edit files?

Frozen directories persist because a freeze boundary was set during your session. You need to unfreeze the workspace to remove this boundary and allow edits across all project folders again.

Can I resume edits across all project folders without restarting my session?

Yes, you can resume edits across all project folders without restarting by unfreezing the workspace. This clears the edit boundary and restores comprehensive edit scope while preserving your current session context.

What happens if I run an unfreeze command when no edit boundary is set?

If you run an unfreeze command when no edit boundary is set, the process handles the already cleared state gracefully. It checks the state file in the plugin data directory and takes no action if the freeze is already removed.

When do I need to clear the edit boundary in a bash workspace?

You need to clear the edit boundary in a bash workspace when you want to broaden collaboration during a session or fix a bug across multiple modules that were previously frozen. This allows comprehensive edits without ending the session.