unfreeze

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The /freeze mechanism can lock edits to a subset of directories. unfreeze clears that restriction, allowing edits to propagate across all directories again.

Core Features & Use Cases

  • Remove the existing freeze boundary to restore full edit access during a session.
  • Use during debugging or collaborative work when broader write permissions are needed.
  • Works within the gstack workflow to widen scope without restarting the session.

Quick Start

Run this skill to clear the current freeze boundary and resume unrestricted edits.

Frequently Asked Questions about unfreeze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove edit restrictions and unfreeze directories in a bash workspace?

To unfreeze directories, you need to remove the freeze boundary file restricting write access. This restores unrestricted edits across all directories within your bash workspace session.

Why are my edits locked to a subset of directories during a debugging session?

Edits are locked because a freeze boundary file was previously set. This restriction limits write access to specific directories until the boundary file is deleted to restore full permissions.

Can I restore full edit access without restarting my bash workspace session?

Yes, you can restore full edit access by deleting the freeze boundary file. This action widens the scope of your current session without requiring a restart.

What is a freeze boundary in state management and when do I need to clear it?

A freeze boundary is an edit restriction limiting writes to specific directories. You need to clear it during collaborative work or debugging when broader access is required.

Do I need a writable state directory to unfreeze workspace edits?

Yes, a writable state directory is required to unfreeze workspace edits. The process uses a bash snippet to delete the freeze boundary file if it is present.

What's the best way to unblock a frozen session when broader write permissions are needed?

The best way to unblock a frozen session is to clear the freeze boundary using a simple bash snippet. This restores full edit access across all directories for collaborative work.