unfreeze
by garrytanThe unfreeze skill clears the freeze boundary set by /freeze, allowing edits across all directories again without ending the session. Use unfreeze when you need to unlock edits, restore full access, or continue a Workflow Automation session after temporary restrictions. It is a focused control skill with straightforward unfreeze usage.
This skill scores 66/100, which is enough to list it for directory users who need a focused /unfreeze action. The repository gives a clear trigger, a concrete Bash workflow, and a direct behavioral outcome (clear the freeze boundary), but it lacks supporting docs and broader usage context, so adopters should expect a narrow, somewhat self-explanatory utility rather than a fully documented workflow package.
- Clear triggerability: the frontmatter names the skill and maps it to phrases like "unfreeze edits," "unlock all directories," and "remove edit restrictions."
- Concrete operational path: the body includes a Bash snippet that removes `freeze-dir.txt` and prints the result, so an agent has an executable action instead of guesswork.
- Specific utility: it directly reverses the `/freeze` state boundary and tells the user to re-run `/freeze` if they want to re-freeze.
- Minimal ecosystem support: there are no scripts, references, resources, or README files to explain broader behavior or integration details.
- Narrow install value: the skill appears to do one small state change, so users looking for richer orchestration or edge-case handling may need extra prompting.
Overview of unfreeze skill
What unfreeze does
The unfreeze skill clears the freeze boundary previously set by /freeze, so edits are allowed across all directories again without ending the session. It is a narrow control skill, not a broad workflow assistant, and it is best used when you need to widen edit scope after a temporary restriction.
Who should use it
Use the unfreeze skill if your workflow depends on controlled edit boundaries and you need to switch from restricted changes back to full access. It is most relevant for users of Workflow Automation who are already using /freeze and want a reliable way to unlock edits without rebuilding the session state.
Why it matters
The main value of unfreeze is speed and clarity: it removes the guesswork of manually resetting state, and it tells the user what changed. That makes it a practical fit when you care about quick session recovery, not just a one-off prompt that says “allow edits.”
How to Use unfreeze skill
Install unfreeze
Use the repository’s skill install flow for gstack and add the unfreeze skill, then verify the skill is available in your skill directory before relying on it in a live session. A typical install path is the gstack skill manager flow; once installed, the skill should be callable as /unfreeze in the same environment that supports /freeze.
Give the right input
The unfreeze usage is simple: ask to remove the freeze boundary, unlock edits, or allow all directories. Good prompts are short and explicit, for example: “Run unfreeze to remove the current freeze boundary and confirm all directories are editable again.” Avoid vague requests like “fix access,” which can leave the agent unsure whether you want full unfreeze, partial scope changes, or a session reset.
What the skill actually checks
The implementation looks for the freeze state file, clears it if present, and reports the result back to you. In practice, that means the important input is not a long task description but the state you expect: whether /freeze was active, whether you want the boundary removed, and whether you want the result confirmed before continuing with edits.
Best workflow
Read SKILL.md first to confirm the exact behavior, then inspect SKILL.md.tmpl if you want the source template behind the generated doc. For this unfreeze skill, there are no extra rules, scripts, or reference folders to chase, so the decision point is straightforward: install it if you need boundary control, and use it when the session is blocked by a previous freeze state.
unfreeze skill FAQ
Is unfreeze only useful after /freeze?
Yes. The unfreeze skill is designed to clear the boundary created by /freeze. If you are not working with a freeze-based edit restriction, a plain prompt may be enough and this skill may add little value.
How is unfreeze different from a normal prompt?
A normal prompt can ask for broader access, but it does not guarantee the session state changes in the same controlled way. The unfreeze skill is better when you need a specific, repeatable action: remove the freeze boundary and restore edits across directories.
Is unfreeze beginner-friendly?
Yes, because the action is simple and the confirmation message is explicit. The main thing beginners need to know is that unfreeze does not start a new workflow; it only removes the current edit restriction so work can continue.
When should I not use unfreeze?
Do not use unfreeze if you still want the current restriction to stay in place, or if you are trying to limit edits for safety, review, or staging. In those cases, keeping /freeze active is the better choice.
How to Improve unfreeze skill
Be precise about the state you want changed
The strongest unfreeze requests name the restriction explicitly: “clear the freeze boundary,” “unlock all directories,” or “remove edit restrictions.” That helps avoid ambiguity with unrelated permission issues, especially in Workflow Automation setups where multiple controls may exist.
Start from the smallest useful context
If the session already knows you used /freeze, say that directly. For example: “We froze edits earlier; run unfreeze now and confirm the boundary is gone.” That is better than describing your whole project, because the skill only needs the session-state change, not the rest of the task.
Check the result before continuing
The best outcome is not just running unfreeze, but verifying that the result message says edits are allowed everywhere. If the boundary is not cleared, re-read SKILL.md and confirm you are using the same environment that registered the freeze state.
Re-freeze only when you need it
After unfreeze, the session hooks remain available, but they no longer block edits because the state file is gone. If you need to narrow scope again later, run /freeze again rather than assuming the previous restriction will return automatically.