unfreeze ยท diff
v0.1.0 to v0.1.0
1 added, 1 removed. Audit A to A.
---
name: unfreeze
version: 0.1.0
description: |
Clear the freeze boundary set by /freeze, allowing edits to all directories
again. 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".
+ "allow all edits". (gstack)
allowed-tools:
- Bash
- Read
---
<!-- AUTO-GENERATED from SKILL.md.tmpl โ do not edit directly -->
<!-- Regenerate: bun run gen:skill-docs -->
# /unfreeze โ Clear Freeze Boundary
Remove the edit restriction set by `/freeze`, allowing edits to all directories.
```bash
mkdir -p ~/.gstack/analytics
echo '{"skill":"unfreeze","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "unknown")'"}' >> ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null || true
```
## Clear the boundary
```bash
STATE_DIR="${CLAUDE_PLUGIN_DATA:-$HOME/.gstack}"
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 are still registered for the
session โ they will just allow everything since no state file exists. To re-freeze,
run `/freeze` again.