← LeaderboardThe Skill Leaderboard

unfreeze

Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)

Published by garrytan ↗garrytan/gstack

Try your first task

unfreeze

Start a fresh conversation.

Use unfreeze to remove the active freeze boundary so edits are allowed across all directories again, and report the result. If the freeze state is busy or unexpected, leave it untouched and explain the recovery needed.

    Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

    SKILL.md

    name: unfreezeversion: 0.1.0description: Clear the freeze boundary set by /freeze, allowing edits to all directories again. (gstack)triggers:   - unfreeze edits  - unlock all directories  - remove edit restrictionsallowed-tools:   - Bash  - Read

    /unfreeze — Clear Freeze Boundary

    Remove the edit restriction set by /freeze, allowing edits to all directories.

    GSTACK_STATE_ROOT=$(~/.claude/skills/gstack/bin/gstack-paths --get GSTACK_STATE_ROOT); : "${GSTACK_STATE_ROOT:?gstack-paths failed; reinstall with ./setup or /gstack-upgrade}"
mkdir -p "$GSTACK_STATE_ROOT"/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_STATE_ROOT"/analytics/skill-usage.jsonl 2>/dev/null || true

    Clear the boundary

    bash "$HOME/.claude/skills/gstack/freeze/bin/freeze-state.sh" clear

    This is explicit user-requested removal, not investigation cleanup. The shared writer serializes it with acquisition, replacement and owner-checked release. On FREEZE_BUSY or unexpected state, leave everything untouched and report recovery; never delete state or a possibly active mutation lock directly.

    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.