Agent skill · Code Review & Quality

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 hook.

oliver-kriskagithub.com/oliver-kriskaGitHub ↗
claude-codeMIT
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill freeze --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Path: plugins/elixir-phoenix/skills/freeze/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Freeze — 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 `/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) | ### Freeze all edits (investigation mode) ```bash mkdir -p .claude && : > .claude/.freeze echo "Freeze ON — all edits blocked. Lift with /phx:freeze off" ``` ### Scope edits to specific directories ```bash 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 `$AR

What's inside
Steps it walks through
  1. Usage
  2. Freeze all edits (investigation mode)
  3. Scope edits to specific directories
  4. Show status
  5. Lift the lock
  6. Iron Laws
  7. Notes
Commands it runs
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"
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"
More from claude-elixir-phoenix
All skills →
watch-prWatch an Elixir/Phoenix PR for new review comments (bot + human) and CI results via a background…Code Review & Qualityphx-deps-auditAudit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes…Securitylab:autoresearchSelf-improving loop for plugin skills. Reads program.md, proposes one mutation per iteration…AI & Agentsdeps-auditAudit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes…Securitysession-scanCompute metrics for Claude Code sessions. Discovers via ccrider, filters trivial, computes…AI & Agentsphx-watch-prWatch an Elixir/Phoenix PR for new review comments (bot + human) and CI results via a background…Code Review & Quality
About this skill
What does the freeze skill do?

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.

How do I install it?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill freeze --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.