unfreeze

Remove the freeze boundary from STATE_DIR to allow edits across all directories.

1|2|Updated Jan 4, 2024
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill unfreeze-nakmiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/unfreeze
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill unfreeze-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories.

Core Features & Use Cases

  • Removes the persistent freeze boundary from the state store, enabling edits across all project directories.
  • Provides a safe no-op path when no boundary is set and preserves existing /freeze hooks for future re-freezing.
  • Works in standard development environments by reading state from STATE_DIR and reporting the prior boundary for auditability.

Quick Start

Run the unfreeze action to clear the freeze boundary and restore full editing access across your workspace.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove a freeze boundary to allow edits across all project directories?

The unfreeze action clears the freeze boundary from the state store, enabling workspace edits across all project directories. It reads the state directory for a boundary marker and removes it to restore full editing access.

What happens if I try to unfreeze my workspace when no freeze boundary is set?

When no freeze boundary is set, unfreeze provides a safe no-op path that does nothing harmful. It simply reports that no boundary was present, ensuring workspace safety without causing errors during standard development sessions.

Does unfreezing a workspace delete the freeze hooks needed for future state locking?

Unfreezing a workspace does not delete freeze hooks. It only removes the persistent boundary marker from the state store while keeping all existing freeze hooks intact for potential re-freezing and future workspace safety checks.

How do I resume refactoring across multiple folders after a workspace freeze?

To resume refactoring across multiple folders after a workspace freeze, run the unfreeze action. It removes the active boundary marker, reports the previous boundary for auditability, and restores edit permissions across the directories.

Can I audit the previous freeze boundary after restoring edit access to my directories?

You can audit the previous freeze boundary after restoring edit access because the unfreeze action reports the prior boundary marker from the state directory before deleting it. This maintains auditability for your development safety workflows.