unfreeze

Clear the edit restriction set by /freeze to enable edits everywhere.

Updated Mar 11, 2026

Search Tags:#session #local #workflows #boundary #edits #gstack #unfreeze

Ready to run

npx skills add https://github.com/kinetas/ai_coding_web --skill unfreeze-kinetas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/kinetas/ai_coding_web/tree/main/gstack/unfreeze
Command: npx skills add https://github.com/kinetas/ai_coding_web --skill unfreeze-kinetas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Quickly lift a local freeze to resume work across the entire project workspace.
Maintain session continuity by keeping session hooks intact while expanding edit scope.
Use during debugging or refactoring when you need to modify files outside the previously frozen subset.

Quick Start

Clear the freeze boundary to enable edits everywhere.

Frequently Asked Questions about unfreeze

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

FAQPage Schema

How do I remove directory edit restrictions during a local development session?▼

Clearing edit restrictions during a local development session requires clearing the boundary set by a previous freeze. This unlocks edits across all directories and local project workspace trees while preserving existing session hooks.

What happens to my session hooks when I unfreeze edit boundaries?▼

When you unfreeze edit boundaries, your session hooks remain fully intact. The process clears the directory restriction while maintaining session continuity, allowing you to resume broader work without losing your existing local workflow setup.

Do I need a specific state file to unlock edits across all directories?▼

Yes, unlocking edits across all directories requires a local state file located at $STATE_DIR/freeze-dir.txt. The Skill reads this file to identify and clear the freeze boundary, enabling edits everywhere in your workspace.

Can I expand my edit scope to files outside a frozen subset when debugging?▼

Yes, you can expand your edit scope to files outside a frozen subset when debugging. Clearing the freeze boundary lifts the restriction, enabling modifications across the entire workspace tree for active development sessions.

When should I clear the freeze boundary in my local project workflows?▼

You should clear the freeze boundary in local project workflows when you need to modify files outside the previously frozen subset, such as during debugging or refactoring, and require edit access across the entire workspace.