unfreeze

Delete the freeze state file to remove edit restrictions across workspace directories.

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill unfreeze-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack/unfreeze
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill unfreeze-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you use the /freeze command to restrict edits to specific directories for focused work, you cannot modify other parts of the workspace until you clear that restriction. This skill removes the freeze boundary so you can edit all directories again without ending your current session.

Core Features & Use Cases

  • Freeze Boundary Removal: Deletes the stored freeze state file to lift all edit restrictions set by /freeze.
  • Session-Persistent Workflow: Lets you widen your edit scope mid-session without losing your current work context.
  • Use Case: If you froze edits to only the /src folder while implementing a new feature, you can use this skill to unlock edits to documentation and configuration files once you finish the core implementation work.

Quick Start

Use the unfreeze skill to clear the current edit freeze and allow unrestricted changes to all workspace 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 in my workspace after using a freeze command?

To remove edit restrictions, you need to clear the freeze boundary by deleting the stored freeze directory configuration file. This action lifts the edit scope limitations, enabling unrestricted modifications across all workspace directories without ending your current session.

Can I expand my edit scope to all directories without restarting my development session?

Yes, you can expand your edit scope mid-session by clearing the current freeze state. Removing the stored freeze configuration file lifts the directory restrictions, which allows you to modify files outside of your originally frozen folders without losing your current work context.

What is a freeze boundary in a development workflow?

A freeze boundary is a temporary edit restriction applied to specific workspace directories for focused tasks. It limits modifications to a targeted scope, ensuring changes are only made within designated folders until the restriction is explicitly cleared.

How do I unlock workspace access for configuration files after freezing edits to source code?

To unlock workspace access for configuration files, you must clear the active edit freeze. Deleting the stored freeze directory configuration file resets the edit scope, which restores your ability to modify unrestricted files like documentation across all directories.

Does clearing an edit freeze affect my current work context?

Clearing an edit freeze does not affect your current work context. Removing the freeze boundary simply deletes the stored configuration file to widen your edit permissions, allowing unrestricted modifications across all workspace directories while keeping your active session intact.

Why are my edits blocked outside of a specific folder in my workspace?

Your edits are blocked because an active freeze boundary is limiting your edit scope to specific directories. Deleting the stored freeze directory configuration file will remove this restriction and restore unrestricted modification access across the workspace.