Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)
ad84005Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".
Remove the edit restriction set by /freeze, allowing edits to all directories.
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
eval "$(~/.claude/skills/gstack/bin/gstack-paths)"
STATE_DIR="$GSTACK_STATE_ROOT"
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/unfreeze · pinned to the source commit
git clone https://github.com/garrytan/gstack.git
cd gstack
git checkout ad8400543cd9ce8d07641362db48d44a95417e33
mkdir -p ".claude/skills/unfreeze"
cp -r "unfreeze" ".claude/skills/unfreeze"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit ad8400543cd9. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
Uses encoding/eval patterns that can hide executable content.
Evidence: [redacted]· fingerprint 1bbd174404efbce9
Declares shell/exec-level tools that grant wide host access.
Evidence: Bash· fingerprint d1e9567da9a8a4b0