unfreeze

Remove the freeze state file to re-enable edits across all directories.

5|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill unfreeze-timurgaleev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/unfreeze
Command: npx skills add https://github.com/timurgaleev/vibestack --skill unfreeze-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary that blocks edits, re-enabling modifications across all directories.

Core Features & Use Cases

  • Clear the active freeze boundary by removing the state marker.
  • Restore normal editing workflow in any directory after a /freeze operation.
  • Use in development sessions where you need to resume changes quickly.

Quick Start

Run the /unfreeze command to clear the freeze boundary and re-enable 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 unfreeze edits in my bash workspace after freezing them?

To unfreeze edits in your bash workspace, you need to clear the active freeze boundary by removing the state marker file. This restores normal editing behavior across all directories, allowing you to resume modifications.

What does a freeze boundary do to workspace files?

A freeze boundary blocks edits across all directories by setting a state file marker. It prevents modifications during development sessions until you explicitly clear the boundary to restore normal editing behavior.

How do I restore editing permissions across all directories?

You restore editing permissions across all directories by running the unfreeze command. It checks for the presence of the freeze state file and removes it, immediately re-enabling modifications in your workspace.

Can I resume editing in a specific directory without unfreezing everything?

No, the unfreeze command clears the freeze boundary across all directories. It removes the global state file to restore normal editing behavior everywhere, rather than targeting a specific directory.

Why are my edits still blocked after trying to unfreeze the workspace?

If edits remain blocked, the freeze state file might still be present. The unfreeze mechanism specifically checks for this state marker and removes it to restore editing capabilities, so ensure the process completes successfully.

Do I need any dependencies to clear the freeze state file?

No dependencies are required to clear the freeze state file. The unfreeze command operates independently to check for and remove the state marker, restoring your workspace editing capabilities without external tools.