unfreeze

Remove gstack freeze edit restrictions and restore repository write access.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill unfreeze-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/yocxy2/gstack3/tree/main/unfreeze
Command: npx skills add https://github.com/yocxy2/gstack3 --skill unfreeze-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the issue of being unable to modify files in restricted directories after a freeze command has been executed, restoring full read-write access to the repository.

Core Features & Use Cases

  • Boundary Removal: Instantly clears the freeze boundary set by the gstack system.
  • Session Flexibility: Allows users to toggle between restricted and unrestricted editing modes without ending their current AI session.
  • Use Case: If you have restricted edits to a specific sub-directory to focus on a task but suddenly need to update a configuration file in the root directory, this skill allows you to unlock the entire project instantly.

Quick Start

Invoke the unfreeze skill to remove all current edit restrictions and allow modifications across the entire repository.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove directory edit restrictions after a freeze command?

To remove directory edit restrictions, you need to clear the boundary set by the freeze command. This action restores full read-write access across the entire repository, allowing modifications to previously locked files.

Can I unlock the repository without ending my current development session?

Yes, you can unlock the repository without ending your current session. This allows you to toggle between restricted and unrestricted editing modes dynamically, providing flexibility to update files anywhere in the project.

What are directory-level edit boundaries and how do they work?

Directory-level edit boundaries restrict file modifications to specific sub-directories, helping you focus on tasks. They are imposed by a freeze command and must be cleared to allow read-write access to the full repository environment.

Why does my repository have read-only access after restricting edits to a sub-directory?

Your repository has read-only access because a freeze command imposed state files restricting edits. To regain full read-write access, you must remove these state files and reset the environment's edit boundary.

What is the best way to transition from focused directory editing to full repository access?

The best way to transition to full repository access is to clear the freeze boundary and remove state files. This instantly unlocks the project, enabling seamless transitions between focused modes and unrestricted modifications.