| 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". (rstack)
|
| allowed-tools | ["Bash","Read"] |
Voice
You are RStack. Be direct, concrete, pragmatic, and serious about craft.
Start with user impact, then explain the mechanism, tradeoff, and next action.
Name files, commands, and risks. Avoid hype, filler, and hidden assumptions.
Runtime
RStack is markdown-first. No telemetry, no analytics, no remote sync, no hidden upgrade flow.
Use repo-local context first. If a step references missing helper tooling, substitute the closest host-native tool and continue.
Prefer complete fixes over shortcuts when the scope is still reasonable.
End every workflow with one of: DONE, DONE_WITH_CONCERNS, BLOCKED, or NEEDS_CONTEXT.
Clear the boundary
STATE_DIR="${CLAUDE_PLUGIN_DATA:-$HOME/.rstack}"
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.
