ha:freeze
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse
SKILL.mdskills/freeze/SKILL.md
GitHubFreeze — scoped edit lock
Toggle a project-local edit lock so Claude can only modify the files you intend
during a focused task (debugging, a tight refactor, a review pass). Enforced by
the freeze-gate.sh PreToolUse hook, which denies Edit/Write/NotebookEdit
outside the allow-list. No sentinel = no lock; the hook stays dormant.
The lock lives in .claude/.freeze — one allowed path prefix per line,
project-relative. Empty file = freeze everything.
Usage
/ha:freeze [args] — resolve $ARGUMENTS and run the matching Bash branch.
| Invocation | Effect |
|---|---|
/ha:freeze |
Freeze ALL edits — read-only investigation mode |
/ha:freeze homeassistant/components/hue tests/components/hue |
Allow edits only under these dirs |
/ha:freeze status |
Show current lock state |
/ha:freeze off |
Lift the lock (delete the sentinel) |
Freeze all edits (investigation mode)
mkdir -p .claude && : > .claude/.freeze
echo "Freeze ON — all edits blocked. Lift with /ha:freeze off"
Scope edits to specific directories
mkdir -p .claude
printf '%s\n' homeassistant/components/hue tests/components/hue > .claude/.freeze
echo "Freeze ON — edits limited to: homeassistant/components/hue tests/components/hue"
Map $ARGUMENTS to the dirs the user named. Include any directory you still need
to write to — e.g. add .claude if progress/scratchpad logging must continue.
Show status
if [ -f .claude/.freeze ]; then
if [ -s .claude/.freeze ]; then echo "Freeze ON — limited to:"; cat .claude/.freeze
else echo "Freeze ON — ALL edits blocked"; fi
else echo "Freeze OFF — no edit lock"; fi
Lift the lock
rm -f .claude/.freeze && echo "Freeze OFF — edits unlocked"
Iron Laws
- MANAGE the sentinel via Bash only (
:>,printf,rm) — NEVER via Edit/Write. The freeze hook gates Edit/Write and would block you from re-scoping or clearing the lock. - NEVER leave a freeze active across unrelated tasks — it persists until
/ha:freeze off, including into later sessions. Clear it when the task ends. - PATHS ARE PROJECT-RELATIVE PREFIXES, one per line —
homeassistant/components/hueallowshomeassistant/components/hueand everything under it; it does NOT allowhomeassistant/components/hue_legacy.
Notes
- The hook denies with a reason and tells Claude not to retry, so a frozen edit surfaces clearly instead of failing silently.
- Pairs with
/ha:investigate(freeze all while root-causing — e.g. tracing down a bad config-entry migration (async_migrate_entry) without risking an accidental edit to it) and/ha:work(scope to the plan's dirs). The lock is advisory tooling, not a security boundary — anyone can run/ha:freeze off.