gstack-unfreeze

Clear the edit freeze boundary to re-enable edits across claude/gstack directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The freeze boundary set by /freeze restricts edits to a subset of directories; this Skill clears that boundary to re-enable edits across the workspace.

Core Features & Use Cases

  • Clears the active freeze boundary to restore full editing scope across claude/gstack work areas.
  • Supports temporary widening of access during an ongoing session without restarting.
  • Safely toggles the boundary and can be re-applied with /freeze to restore restrictions.

Quick Start

Use the unfreeze command to remove the current edit freeze and enable edits everywhere.

Frequently Asked Questions about gstack-unfreeze

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

FAQPage Schema
How do I unfreeze edits in a claude-code workspace session?

To unfreeze edits in a claude-code workspace, you clear the active freeze boundary to restore full directory access. This action re-enables modifications across all claude and gstack directories without requiring a session restart.

What does an edit freeze boundary do in bash session management?

An edit freeze boundary restricts file modifications to a specific subset of directories within your workspace. It limits the modification scope during a bash session, ensuring changes only occur in approved locations until explicitly cleared.

Can I re-apply directory edit restrictions after unfreezing a workspace?

Yes, you can re-apply directory edit restrictions after unfreezing a workspace. The unfreeze action safely toggles the boundary off, allowing you to use the freeze command again to restore the restricted modification scope.

How does the unfreeze command safely restore full directory access?

The unfreeze command safely restores directory access by toggling a stored state file named freeze-dir.txt under the state directory. It only modifies the boundary when this file exists, preventing unintended access changes.

Why are my edits restricted to a subset of directories in my gstack workspace?

Your edits are restricted because a freeze boundary was previously applied to your gstack workspace. This boundary limits modifications to a specific subset of directories and requires an explicit unfreeze action to restore full access.