unfreeze

Clear the persisted freeze boundary file to allow edits across all repository directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of being stuck in a restricted editing scope after a freeze boundary has been set, preventing the assistant from modifying files outside the initially allowed directories.

Core Features & Use Cases

  • Clears the freeze boundary: Removes the saved boundary state so edits are allowed across all directories.
  • Supports manual control: Designed as a manual trigger only, invoked when the user explicitly types /unfreeze.
  • Session-safe behavior: Keeps session hooks registered from /freeze, but with the state cleared it effectively unlocks edits for the remainder of the session.

Use it when you are asked to “unfreeze”, “unlock edits”, “remove freeze”, or “allow all edits”, such as when an iterative review starts narrow but later requires broader changes across the repository.

Quick Start

Ask the assistant to run /unfreeze to clear the freeze boundary and allow edits everywhere again.

Frequently Asked Questions about unfreeze

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

FAQPage Schema
How do I remove a repository edit freeze to allow modifications in all directories?

To remove a repository edit freeze, invoke the /unfreeze command, which clears the persisted freeze boundary file and restores the assistant's ability to modify all directories across the repository.

Why is my assistant restricted from editing files outside specific directories during a session?

The assistant is restricted because a prior freeze boundary was set, limiting edits to specific directories. You can unlock this scope by running /unfreeze to remove the saved boundary state.

When do I need to widen the editing scope without restarting my coding session?

You need to widen the editing scope when an iterative review starts narrow but later requires broader repository changes. Running /unfreeze clears the restriction without ending your current session.

Does running the unfreeze command remove session hooks registered by the initial freeze command?

Running /unfreeze does not remove session hooks registered by the freeze command. It clears the persisted boundary state, which effectively unlocks edits for the remainder of the session.

Can I manually trigger the removal of an edit lock, or is it an automated process?

Removing an edit lock is a strictly manual process triggered by the /unfreeze command. It is designed to be invoked only when you explicitly want to allow edits everywhere again.

What happens to analytics data when I clear the freeze boundary from my repository?

When you clear the freeze boundary, the skill records its usage to a JSONL log under ~/.gstack/analytics and reports whether a boundary was previously set before unlocking the repository.