/freeze — Restrict Edits to a Directory

Lock file edits to a specific directory. Any Edit or Write operation targeting a file outside the allowed path will be blocked (not just warned).

bash
1mkdir -p ~/.gstack/analytics
2echo '{"skill":"freeze","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","repo":"'$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || echo "unknown")'"}'  >> ~/.gstack/analytics/skill-usage.jsonl 2>/dev/null || true

Setup

Ask the user which directory to restrict edits to. Use AskUserQuestion:

• Question: "Which directory should I restrict edits to? Files outside this path will be blocked from editing."
• Text input (not multiple choice) — the user types a path.

Once the user provides a directory path:

1. Resolve it to an absolute path:

bash
1FREEZE_DIR=$(cd "<user-provided-path>" 2>/dev/null && pwd)
2echo "$FREEZE_DIR"

2. Ensure trailing slash and save to the freeze state file:

bash
1FREEZE_DIR="${FREEZE_DIR%/}/"
2STATE_DIR="${CLAUDE_PLUGIN_DATA:-$HOME/.gstack}"
3mkdir -p "$STATE_DIR"
4echo "$FREEZE_DIR" > "$STATE_DIR/freeze-dir.txt"
5echo "Freeze boundary set: $FREEZE_DIR"

Tell the user: "Edits are now restricted to <path>/. Any Edit or Write outside this directory will be blocked. To change the boundary, run /freeze again. To remove it, run /unfreeze or end the session."

How it works

The hook reads file_path from the Edit/Write tool input JSON, then checks whether the path starts with the freeze directory. If not, it returns permissionDecision: "deny" to block the operation.

The freeze boundary persists for the session via the state file. The hook script reads it on every Edit/Write invocation.

Notes

• The trailing / on the freeze directory prevents /src from matching /src-old
• Freeze applies to Edit and Write tools only — Read, Bash, Glob, Grep are unaffected
• This prevents accidental edits, not a security boundary — Bash commands like sed can still modify files outside the boundary
• To deactivate, run /unfreeze or end the conversation