unfreeze

Name: unfreeze
Availability: InStock
Author: cegit27

Remove the /freeze edit restriction to restore modification permissions across project directories.

3|14|Updated Mar 10, 2026

Search Tags:#development workflow #file access #gstack #unfreeze #freeze boundary #edit permissions

Ready to run

npx skills add https://github.com/cegit27/moodle-proctor --skill unfreeze-cegit27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill unfreeze-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you use the /freeze command to limit edit access to specific project directories, you cannot modify files outside that boundary. This Skill removes that restriction so you can edit any part of your project again without ending your current session.

Core Features & Use Cases

Clear Freeze Boundaries: Removes the edit restriction set by the /freeze command instantly.
Preserve Session State: Unlocks edits without terminating your current workflow or losing context.
Use Case: If you froze edits to only the backend/ directory to make safe, scoped changes, use this Skill to unlock the frontend/ and other directories for additional edits without restarting your work.

Quick Start

Use the unfreeze skill to remove the current edit freeze and allow modifications to all project 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 after freezing a directory boundary in my development workflow?▼

To remove edit restrictions after freezing a directory boundary, you need to clear the persisted freeze state stored in the gstack state directory. This restores full modification permissions across all project directories without terminating your current session.

Can I unlock edit access to all project files without ending my current development session?▼

Yes, you can unlock edit access to all project files without ending your current session. This is achieved by clearing the freeze boundary state from the gstack state directory, which preserves your workflow context while restoring unrestricted modifications.

What happens to my session state when I clear a freeze boundary to restore file modifications?▼

Clearing a freeze boundary to restore file modifications preserves your existing session state entirely. It unlocks edits across all project directories without restarting your workflow or losing the context of the changes you were previously scoping.

How to unfreeze project directories to allow unrestricted edits outside a scoped boundary?▼

To unfreeze project directories and allow unrestricted edits, you must clear the persisted freeze boundary state stored in the gstack state directory. This removes the edit access restriction and restores full modification permissions across the entire project.

Why does the freeze boundary prevent file modifications outside a specific project area?▼

The freeze boundary prevents file modifications outside a specific project area because the /freeze command limits edit access to a defined scope. This restriction is persisted in the gstack state directory to ensure safe, scoped changes during development.

Do I need to restart my workflow to modify files outside a frozen edit boundary?▼

No, you do not need to restart your workflow to modify files outside a frozen edit boundary. You can clear the persisted freeze state in the gstack directory to restore full modification permissions while preserving your current session state.