unfreeze

Clear the edit boundary established by /freeze on the workspace.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the edit restriction 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".

Core Features & Use Cases

  • Clear the current edit boundary to enable universal changes across the workspace.
  • Safe and predictable: if no boundary is set, informs the user and does nothing.
  • Use case: after a freeze, you can proceed with edits across all project folders without restarting the session.

Quick Start

Clear the freeze boundary to permit edits 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 an edit boundary and unfreeze my workspace directories?

To unfreeze your workspace, you need to remove the edit boundary established by a freeze command. This action clears the restriction file, allowing universal changes across all project directories without restarting your session.

What happens if I try to remove a freeze boundary when no freeze is active?

If no freeze boundary is active, attempting to remove the freeze is safe and predictable. The process simply checks the state file, finds no boundary to remove, informs the user, and does nothing.

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

To unlock edits without ending your bash session, you remove the current edit boundary. This widens your edit scope to permit modifications across all project folders immediately within the active workflow.

Do I need to configure a specific state file path before removing an edit boundary?

Removing an edit boundary uses a state file located at a configured path to check for and remove the boundary file. You must ensure your workflow control environment is set up to manage this state configuration.

Can I use workflow control commands to allow all edits after applying directory restrictions?

Yes, workflow control commands can allow all edits after applying directory restrictions. Clearing the freeze boundary safely restores full access to modify any directory, overriding the previous edit scope limitations.