unfreeze

Remove the freeze-dir.txt edit boundary to re-enable edits across all directories.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/apeejay-education/cadencesprout --skill unfreeze-apeejay-education
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/apeejay-education/cadencesprout/tree/main/.agents/skills/gstack-unfreeze
Command: npx skills add https://github.com/apeejay-education/cadencesprout --skill unfreeze-apeejay-education

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 active edit boundary to enable full directory edits during a session.
  • Detects whether a freeze boundary exists and provides a clear result to the user.
  • Works with existing /freeze hooks to preserve session continuity.

Quick Start

Tell the agent to unfreeze to remove the current edit restrictions 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 unlock edit restrictions and allow full directory edits again?

To unlock edit restrictions, the unfreeze command checks STATE_DIR for a freeze-dir.txt file and removes it if found, clearing the edit boundary and re-enabling edits across all directories.

What happens to my session hooks when I remove a freeze boundary?

When you remove a freeze boundary, existing /freeze hooks remain registered for the session, preserving session continuity while allowing edits to all directories without ending the current session.

Can I widen my edit scope without ending the current shell session?

Yes, you can widen edit scope without ending the session by clearing the freeze boundary, which removes the freeze-dir.txt state file and re-enables full directory edits while keeping the session active.

Why are my directory edits still blocked after a temporary lock?

Directory edits remain blocked because the freeze-dir.txt state file still exists in STATE_DIR, and clearing it requires running the unfreeze command to remove the active edit boundary and restore full edit access.

How do I know if an edit boundary is currently active in my session?

The unfreeze command detects whether a freeze boundary exists by checking for a freeze-dir.txt file in STATE_DIR, providing a clear result to the user about the current edit restriction status.

When should I use the unfreeze command to restore directory editing?

Use the unfreeze command when you need to widen edit scope during a session or after a temporary lock, such as when asked to unfreeze, unlock edits, remove freeze, or allow all edits across directories.