unfreeze

Remove the freeze-dir.txt indicator to restore full repository editing privileges.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill unfreeze-txema-puch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/txema-puch/drone-ai-saturdays/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill unfreeze-txema-puch

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

  • Re-enable edits across the repository after a freeze, restoring full working scope during a session.
  • Safe and reversible: removes the state flag and reports the new edit boundary to the user.
  • Use case: you need to resume active development across multiple folders after constraining edits for a planning phase.

Quick Start

Run the unfreeze command to remove the freeze boundary and restore full edit access.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove an edit freeze boundary in my repository?

To remove an edit freeze boundary, the unfreeze command deletes the state indicator file (freeze-dir.txt) if present and records the operation, ensuring subsequent edits are allowed and the session state is updated.

Can I unlock edits across all directories without ending my current shell session?

Yes, you can unlock edits across all directories without ending your current shell session. The unfreeze command widens the edit scope and restores full repository editing privileges during interactive sessions.

What does unfreezing edits mean for my workflow state?

Unfreezing edits means clearing the freeze boundary to restore full repository editing privileges. It removes the state indicator file and reports the new edit boundary, ensuring subsequent edits are allowed and the session state is updated.

Is removing the edit freeze safe and reversible during development?

Yes, removing the edit freeze is safe and reversible. The command removes the state flag, reports the new edit boundary to the user, and allows you to resume active development across multiple folders after constraining edits for a planning phase.

When should I re-enable edits across the repository after constraining them?

You should re-enable edits across the repository when you need to resume active development across multiple folders after constraining edits for a planning phase, or when prompted to unfreeze, unlock edits, remove freeze, or allow all edits.