Clear the freeze boundary set by /freeze, allowing edits to all directories again.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add timurgaleev/vibestack --skill unfreeze --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Unfreeze?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/timurgaleev-unfreeze)More formats (shields.io, HTML) on the badges page.
---
name: unfreeze
description: |
Clear the freeze boundary set by /freeze, allowing edits to all directories again.
allowed-tools:
- Bash
- Read
triggers:
- unfreeze edits
- unlock all directories
- remove edit restrictions
- allow all edits
- exit careful mode
---
## When to invoke
Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".
# /unfreeze — Clear Freeze Boundary
Remove the edit restriction set by `/freeze`, allowing edits to all directories.
```bash
STATE_DIR="${VIBESTACK_HOME:-$HOME/.vibestack}"
if [ -f "$STATE_DIR/freeze-dir.txt" ]; then
PREV=$(cat "$STATE_DIR/freeze-dir.txt")
rm -f "$STATE_DIR/freeze-dir.txt"
echo "Freeze boundary cleared (was: $PREV). Edits are now allowed everywhere."
else
echo "No freeze boundary was set."
fi
```
Tell the user the result. Note that `/freeze` hooks remain registered for the
session — they will allow all paths since no state file exists. To re-freeze,
run `/freeze` again.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...