Unfreeze

Remove edit restrictions from all directories previously frozen by '/freeze'.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill unfreeze-aporto-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Unfreeze
Source: https://github.com/aporto-tech/aporto-agent-skills/tree/main/skills/gstack/unfreeze
Command: npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill unfreeze-aporto-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill resolves the issue of edit restrictions imposed by the '/freeze' command, enabling all directories to be edited again.

Core Features & Use Cases

  • Remove Edit Restrictions: Lifts the freeze boundary that prevents directory edits.
  • Edit Scope Widening: Allows for edits without ending the session.
  • Use Case: Ideal when a user is requested to 'unfreeze', 'unlock edits', 'remove freeze', or 'allow all edits' within the gstack environment.

Quick Start

Execute the command "unfreeze" to remove the edit restrictions and allow editing in all directories.

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 from a frozen session?

Yes, you can unlock directory edits without ending your session by running the 'unfreeze' command. It lifts the edit restrictions previously established by the '/freeze' command, widening your edit scope immediately.

Why does the unfreeze command fail to allow all edits?

The unfreeze command fails if the '/freeze' state file is not present. It requires this specific state file to detect and clear the existing freeze boundary, allowing all directories to be edited again.

What is the best way to resume editing in all directories after a freeze?

The best way to resume editing in all directories is to run the 'unfreeze' command. It targets and clears the edit restrictions set by '/freeze', restoring full directory access without restarting your environment.

Does the gstack environment require a specific state file to remove freeze restrictions?

Yes, the gstack environment requires the '/freeze' state file to be present for the 'unfreeze' command to work. This file acts as the trigger for clearing edit restrictions and widening the edit scope.