unfreeze

Remove the freeze boundary to re-enable edits across gstack-managed directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories within the session.

Core Features & Use Cases

  • Unfreezes edits across all gstack-managed directories.
  • Re-enables changes after a temporary restriction to support focused work.
  • Works within a running gstack session by clearing the stored freeze state.

Quick Start

Run the unfreeze operation to remove the freeze boundary and restore full edit access to 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 a gstack-managed directory?

To unfreeze edits, run the unfreeze operation to clear the stored freeze state marker, restoring full edit access to all directories within your gstack session.

What happens when I remove the freeze boundary in a shell session?

Removing the freeze boundary clears the stored state marker, re-enabling changes and making all previously restricted gstack-managed directories editable again.

Why are my edits restricted to a single directory after a focused work session?

Edits are restricted because a freeze boundary was set to limit scope. You must clear the stored state marker in the plugin data directory to unlock edits across all directories.

Does unfreezing edits require any special dependencies or shell components?

No dependencies are required. The unfreeze operation runs a simple shell routine that clears the freeze marker from the CLAUDE plugin data directory.

When should I clear the freeze state in gstack?

Clear the freeze state when you want to widen edit scope within a session or re-enable changes across all gstack-managed directories after finishing focused work.

Can I unlock edits for all directories at once during a running session?

Yes, running the unfreeze operation works within a running gstack session to remove the freeze boundary and restore full edit access to all directories simultaneously.