unfreeze
Removes the edit restriction set by the `/freeze` command, allowing modifications to all directories. It deletes the freeze boundary file, restoring the project to an editable state and enhancing development flexibility.
git clone https://github.com/garrytan/gstack.gitBefore / After Comparison
1 组Manually locating and deleting the freeze state file can be time-consuming or error-prone due to unfamiliar paths or operational mistakes, impacting development efficiency.
One-click unfreeze via the `/unfreeze` command instantly restores editing permissions for all directories, avoiding manual hassle and potential errors, significantly improving workflow fluidity.
/unfreeze — Clear Freeze Boundary
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
Clear the boundary
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.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill