Stats
Actions
Tags
From Darkroom Engineering
Restricts Edit/Write/MultiEdit to one directory for the session, blocking edits outside it. Useful for debugging or fencing parallel agents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/darkroom:freezeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Restrict `Edit`, `Write`, and `MultiEdit` to a single directory. Any edit targeting a file outside the boundary is **blocked** by the `freeze-guard` PreToolUse hook. State persists for the session in `~/.claude/tmp/freeze.json`.
Restrict Edit, Write, and MultiEdit to a single directory. Any edit targeting a file outside the boundary is blocked by the freeze-guard PreToolUse hook. State persists for the session in ~/.claude/tmp/freeze.json.
Note: notebook edits (NotebookEdit) and shell writes (Bash) are not gated — the boundary covers the file-editing tools only.
If the user named a directory, use it. Otherwise ask which directory to lock to (AskUserQuestion, free-text path). Then run, substituting the chosen path for PATH:
bun ~/.claude/src/scripts/freeze.ts set "PATH"
Confirm to the user that edits are now restricted to that path, and that they can lift it any time with "unfreeze".
bun ~/.claude/src/scripts/freeze.ts off
bun ~/.claude/src/scripts/freeze.ts status
npx claudepluginhub darkroomengineering/cc-settings --plugin darkroomRestricts Edit and Write operations to a specific directory for the session. Blocks edits outside the allowed path. Useful when debugging to prevent accidentally modifying unrelated code.
Hard-blocks edits outside declared frozen directories to protect critical paths during risky changes.
Prevents destructive operations on production systems and autonomous agents by intercepting dangerous commands, restricting edits to a directory, or combining both protections.