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 hook.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
/phx:freeze [args] — resolve $ARGUMENTS and run the matching Bash branch.
| Invocation | Effect |
|---|---|
/phx:freeze | Freeze ALL edits — read-only investigation mode |
/phx:freeze lib/app_web priv/repo | Allow edits only under these dirs |
/phx:freeze status | Show current lock state |
/phx:freeze off | Lift the lock (delete the sentinel) |
mkdir -p .claude && : > .claude/.freeze
echo "Freeze ON — all edits blocked. Lift with /phx:freeze off"
mkdir -p .claude
printf '%s\n' lib/app_web priv/repo > .claude/.freeze
echo "Freeze ON — edits limited to: lib/app_web priv/repo"
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.
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
rm -f .claude/.freeze && echo "Freeze OFF — edits unlocked"
:>, printf, rm) — NEVER via
Edit/Write. The freeze hook gates Edit/Write and would block you from
re-scoping or clearing the lock./phx:freeze off, including into later sessions. Clear it when the task ends.lib/foo allows
lib/foo and everything under it; it does NOT allow lib/foobar./phx:investigate (freeze all while root-causing) and /phx:work
(scope to the plan's dirs). The lock is advisory tooling, not a security
boundary — anyone can run /phx:freeze off.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze a legacy app in any language before rewriting it in Elixir: inventory, features as goals, why each mechanism exists, runtime topology, external contracts. Use to start or refresh a rewrite.
The English summary is being prepared. Showing the original description.
Design the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.
The English summary is being prepared. Showing the original description.
Ash Framework — resources, actions, policies, aggregates; Use when generating resources via mix ash.codegen, editing…
The English summary is being prepared. Showing the original description.
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
The English summary is being prepared. Showing the original description.
Compatibility alias for the Elixir/Phoenix plugin's LiveView assigns audit. Invoke explicitly with /lv:assigns.
The English summary is being prepared. Showing the original description.
Inspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporary_assigns.
The English summary is being prepared. Showing the original description.