unfreeze

Remove the freeze marker to allow edits across all directories.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/onlypfachi/chief --skill unfreeze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/onlypfachi/chief/tree/main/unfreeze
Command: npx skills add https://github.com/onlypfachi/chief --skill unfreeze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you need to widen the edit scope without ending the session. This enables you to resume work across the project without restarting or reinitializing the session.

Core Features & Use Cases

  • Remove the freeze boundary across the workspace to allow edits in all folders.
  • Resume ongoing work after a temporary restriction without restarting the session.
  • Use case: You need to implement a large refactor across multiple directories quickly.

Quick Start

Run /unfreeze to clear the freeze boundary and enable edits across all directories.

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 and unlock all directories in my project?

To remove an edit freeze boundary and unlock directories, you need to clear the stored freeze marker. This action lifts the restriction across the entire workspace, allowing wide-scope edits without restarting your development session.

Why are my edits restricted to a subset of directories during a development session?

Edits are restricted to a subset of directories because an active freeze marker establishes a boundary. This stored marker limits modifications, preventing changes outside the specified scope until the boundary is explicitly cleared.

Can I resume a large refactor across multiple directories without restarting the session?

Yes, you can resume a large refactor across multiple directories without restarting by clearing the freeze boundary. Removing the stored marker instantly widens the edit scope across the entire project workspace.

What is the best way to unlock project-wide edits after applying a temporary directory restriction?

The best way to unlock project-wide edits after a temporary directory restriction is to remove the freeze marker. This deterministic boundary-clearing operation deletes the stored marker, restoring full edit access across all folders.

Does clearing the edit freeze boundary affect the entire project workspace?

Yes, clearing the edit freeze boundary applies across the entire project workspace. It removes the restriction that limits changes to a subset of directories, enabling wide-scope edits throughout all project folders.