unfreeze
GitHub清除由 /freeze 设置的编辑边界，解除目录编辑限制，允许对所有目录进行修改。该技能用于在会话中扩大编辑范围，通过调用脚本清除冻结状态文件，并处理并发冲突。
Trigger Scenarios
Install
npx skills add garrytan/gstack --skill unfreeze -g -y
SKILL.md
Frontmatter
{
"name": "unfreeze",
"version": "0.1.0",
"triggers": [
"unfreeze edits",
"unlock all directories",
"remove edit restrictions"
],
"description": "Clear the freeze boundary set by \/freeze, allowing edits to all directories again. (gstack)",
"allowed-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.
Version History
-
82db89a
Current 2026-11-03 06:46
移除了正文中的“何时调用”章节以优化 token 消耗和路由逻辑，触发说明已迁移至描述或根路由器块。
-
2d42e4e
2026-10-19 13:46
更新状态根路径获取方式，使用 gstack-paths 工具动态获取 GSTACK_STATE_ROOT，替代硬编码的 ~/.gstack/analytics 路径，以支持更灵活的安装和升级场景。
-
01593aa
2026-09-28 05:44
v1.91.2.0: 修复了旧版直接删除状态文件的逻辑，改为调用专用脚本处理序列化与锁检查，提升可靠性。
- a325940 2026-07-25 11:07
