unfreeze

Name: unfreeze
Availability: InStock
Author: kakarottoooo

Remove the freeze marker to re-enable edits across all directories.

Updated Mar 17, 2026

Search Tags:#workflow #session #edit #boundary #state #gstack #unfreeze

Ready to run

npx skills add https://github.com/Kakarottoooo/onegent --skill unfreeze-kakarottoooo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear the edit boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. If there is no boundary set, the command informs the user and remains a no-op. The skill is designed to be safe and reversible, enabling flexible experimentation within an active session.

Core Features & Use Cases

Remove the freeze boundary from the session state so edits can be made anywhere.
Provide safe no-op behavior when no boundary exists and provide clear feedback to the user.
Use case: after a focused debugging session, you can unfreeze to resume broad configuration changes without restarting.
Use in collaboration sessions where multiple contributors need broad editing rights briefly.

Quick Start

Ask the system to unfreeze to enable edits across all directories in the current session.

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 boundary to allow unrestricted writes across all directories in my active session?▼

To remove an edit boundary, you can unfreeze the session state to delete the marker file restricting write access. This re-enables broad modification scope across all directories without needing to restart the session.

What happens if I try to clear an edit boundary when no freeze is set in the session?▼

When no edit boundary is set, clearing the freeze acts as a safe no-op. The system detects that no marker file exists, provides clear feedback that no boundary is set, and makes no changes to the session state.

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

Yes, you can widen your edit scope without ending the workflow by clearing the freeze boundary. This allows broad configuration changes immediately, making it safe and reversible for flexible experimentation within the same active session.

How does clearing a freeze boundary help with collaboration sessions?▼

Clearing a freeze boundary helps collaboration sessions by allowing multiple contributors to briefly gain broad editing rights across all directories. You can remove the write access restriction instantly without terminating the current workflow.

When should I not use an unrestricted edit scope in my workflow?▼

You should not use an unrestricted edit scope when you need focused debugging or isolated changes, as clearing the freeze removes the directory write restriction entirely. You should keep the boundary set to prevent accidental modifications outside the target scope.