unfreeze

Remove the freeze state file to restore edit permissions in gstack sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the edit restriction created by /freeze, enabling edits across all directories again when you need to broaden the scope of work during a session.

Core Features & Use Cases

  • Clears the freeze boundary to permit edits in any directory.
  • Records the action in analytics (optional) and preserves session hooks for future freezes.
  • Works within claude gstack sessions to quickly restore full edit access after a freeze.

Quick Start

Unfreeze the current session to permit edits everywhere.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I unfreeze edit boundaries in a gstack session?

To unfreeze edit boundaries in a gstack session, you clear the freeze boundary state file blocking edits. This action removes the edit lock, permitting modifications across all directories again to widen your session scope.

What happens to session hooks when I clear the freeze boundary?

Clearing the freeze boundary preserves your session hooks for future use. The skill only deletes the current state file restricting edits, keeping hooks intact so you can reapply freeze boundaries later if needed.

How do I restore full edit access across directories after a freeze?

You restore full edit access across directories by clearing the freeze boundary. The skill reads and deletes the state file applied by the freeze command, immediately reporting the updated edit permissions to you.

Can I remove edit restrictions in a claude gstack workflow without losing analytics?

Yes, you can remove edit restrictions without losing analytics. Clearing the freeze boundary records the action in analytics if configured, while it restores full directory edit access within your claude gstack workflow.

Why are edits blocked across directories during my devops session?

Edits are blocked across directories because a freeze boundary state file is active. This lock restricts your edit scope during gstack sessions, requiring you to clear the state file to resume modifications.

Does clearing the freeze boundary work outside of claude gstack workflows?

Clearing the freeze boundary is designed specifically for claude gstack workflows. The skill targets state files created by the /freeze command within those sessions to restore full edit access across directories.