unfreeze

Remove edit restrictions by deleting the stored freeze boundary configuration file.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill unfreeze-jia-hong-peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unfreeze
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/unfreeze
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill unfreeze-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When using the /freeze command to restrict edits to a specific project directory, you may later need to make changes to files outside that boundary without ending your current session. This Skill resolves that limitation by completely removing the edit restriction.

Core Features & Use Cases

  • Clear Freeze State: Deletes the stored freeze boundary configuration file to lift all edit restrictions.
  • Status Reporting: Confirms the previous restricted directory (if one was set) so you have full visibility into what was unlocked.
  • Use Case: You set a freeze on the src/ directory to avoid accidental changes to core frontend code while working on a small UI fix, then need to update a backend API route in functions/api/ — run this Skill to enable edits across the entire project.

Quick Start

Use the unfreeze skill to remove all edit restrictions and allow changes to any directory in your project.

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 without ending my development session?

To remove directory edit restrictions without terminating your active session, delete the stored freeze boundary configuration file. This action lifts the edit limitations and restores unrestricted modification access across all project directories.

How do I unfreeze a project directory to allow edits everywhere?

To unfreeze a project directory and allow edits everywhere, the stored boundary configuration file must be deleted. This clears the freeze state and reports the previously restricted path for full visibility.

What happens to the previous restricted path when I clear the freeze state?

When you clear the freeze state, the system confirms the previous restricted directory path back to you. This status reporting ensures you have full visibility into exactly what directory was unlocked after the boundary file is deleted.

Can I edit files outside the freeze boundary without restarting my workflow?

Yes, you can edit files outside the freeze boundary without restarting your workflow. By deleting the freeze boundary configuration, you lift all edit restrictions and enable unrestricted modifications across the entire project during the active session.

When do I need to remove edit restrictions in a development workflow?

You need to remove edit restrictions in a development workflow when you temporarily set a freeze boundary to prevent accidental changes to sensitive files, but later require to modify files in other directories without terminating the active session.