Menu
Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.
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.
Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow
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.
| 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).