unfreeze

Clears the freeze boundary to restore write access across all project directories.

Updated Sep 10, 2024
One-click install
npx skills add https://github.com/TioSavich/UMEDCTA --skill unfreeze-tiosavich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/TioSavich/UMEDCTA/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/TioSavich/UMEDCTA --skill unfreeze-tiosavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".

Core Features & Use Cases

  • Removes the freeze boundary to restore full workspace edit access when collaboration or exploration is needed.
  • Supports re-applying the freeze after changes by re-issuing the /freeze command to restore scoped edits.

Quick Start

Run the unfreeze command to clear the freeze boundary and allow edits everywhere.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I restore write access to all directories after applying an edit freeze?

An edit freeze restricts write access to specific directories during a session. You unfreeze these directories to restore full workspace edit access when collaboration or exploration is needed without ending the session.

What happens to my existing project data when I remove the edit freeze?

You clear the freeze boundary to restore full workspace edit access during an active session. This allows you to widen your edit scope for collaboration or exploration without terminating the current shell session.

Can I reapply the directory edit freeze after unfreezing the workspace?

Yes, you can re-apply the freeze after making changes by re-issuing the freeze command to restore scoped edits. This allows you to dynamically toggle write access across project directories as needed.

Why does my shell session still have restricted write access after attempting to unfreeze directories?

Yes, clearing the edit freeze boundary supports re-applying the freeze later. You can re-issue the freeze command after making changes to restore scoped edits and restrict write access again.

Does removing the edit boundary execute any destructive actions on my files?

No, unfreezing does not execute destructive actions or delete unrelated data. It safely clears the freeze indicator to restore write access across all project directories without causing data loss.