Menu
Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit context window consumption across LOTRAOM agents, skills, rules, MCP servers, and CLAUDE.md. Report token estimates, flag bloat, recommend trims.
Hard-block Edit/Write outside a chosen directory. Use to scope-lock edits during a focused fix or refactor. Pair with /unfreeze to release.
Six-phase root-cause debugging for crashes, build failures, or "why is this broken" reports. Iron Law - no fixes without root cause. Auto-engages /freeze.
Dispatch an independent Codex verification job for the current changes
Inspect all changed files, group by logical concern, and guide atomic per-concern commits
Check mod compatibility against a new Bannerlord version by reviewing patch targets and GameModel overrides
| 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"] |
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
/freeze's declared hooks remain registered (they're inert without the state file)./freeze again — it overwrites the state file..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.