unfreeze

스타2

포크1

업데이트2026년 4월 26일 12:24

Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

haterade22

haterade22/TAOM

GitHub 저장소 열기 Creator 저장소 보기

다운로드

/unfreeze — Release the Freeze Boundary

Removes the freeze-dir.txt state file. Once cleared, the /freeze skill's PreToolUse hooks will allow every Edit/Write again (because the hook short-circuits to {} when the state file is missing).

STATE_DIR="${CLAUDE_PROJECT_DIR}/.claude/tmp/freeze"
FREEZE_FILE="$STATE_DIR/freeze-dir.txt"

if [[ -f "$FREEZE_FILE" ]]; then
    PREV=$(cat "$FREEZE_FILE")
    rm -f "$FREEZE_FILE"
    echo "Freeze boundary released. Was: $PREV"
else
    echo "No freeze boundary was active."
fi

Notes

This affects only the freeze state file. /freeze's declared hooks remain registered (they're inert without the state file).
If you want to switch boundaries instead of releasing, just run /freeze again — it overwrites the state file.
Ending the conversation also clears the boundary (state file lives in .claude/tmp/freeze/, gitignored, but persists across sessions until manually cleared — re-run /unfreeze if a stale boundary is still active when you start work).

이 저장소의 다른 Skills

같은 저장소

native-crash-triage

haterade22/TAOM

Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.

2026-07-242

codex-verify

haterade22/TAOM

Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results

2026-07-222

commit-split

haterade22/TAOM

Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.

2026-07-222

context-restore

haterade22/TAOM

Load a snapshot saved by /context-save and present it so this session can pick up where the last one left off without re-deriving decisions.

2026-07-222

deep-review

haterade22/TAOM

Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow

2026-07-222

engine-bump

haterade22/TAOM

Respond to a Bannerlord engine update (Steam force-bump or deliberate migration) — preserve the decompile baseline, regen, diff, re-verify bindings and creature data, control-battle.

2026-07-222

name	unfreeze
description	Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.
allowed-tools	["Bash"]

/unfreeze — Release the Freeze Boundary

STATE_DIR="${CLAUDE_PROJECT_DIR}/.claude/tmp/freeze"
FREEZE_FILE="$STATE_DIR/freeze-dir.txt"

if [[ -f "$FREEZE_FILE" ]]; then
    PREV=$(cat "$FREEZE_FILE")
    rm -f "$FREEZE_FILE"
    echo "Freeze boundary released. Was: $PREV"
else
    echo "No freeze boundary was active."
fi

Notes

This affects only the freeze state file. /freeze's declared hooks remain registered (they're inert without the state file).
If you want to switch boundaries instead of releasing, just run /freeze again — it overwrites the state file.
Ending the conversation also clears the boundary (state file lives in .claude/tmp/freeze/, gitignored, but persists across sessions until manually cleared — re-run /unfreeze if a stale boundary is still active when you start work).