All skills
garrytan avatar

/freeze

@01593aa official
by Garry Tangarrytan/gstack135k stars
20,051

Restrict file edits to a specific directory for the session. (gstack)

Use this Skill: https://skilld.dev/gh/garrytan/gstack/freeze

This session only. Nothing lands on disk.

SKILL.md

β‰ˆ19 tokens always: the name and description. β‰ˆ799 when used: this file.

<!-- AUTO-GENERATED from SKILL.md.tmpl β€” do not edit directly --> <!-- Regenerate: bun run gen:skill-docs -->

When to invoke this skill

Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits".

/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).

mkdir -p ~/.gstack/analytics
echo '{"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:

Set the user-selected boundary with the shared state writer. It resolves the physical absolute path and serializes replacement with investigation cleanup:

bash "$HOME/.claude/skills/gstack/freeze/bin/freeze-state.sh" set "<user-provided-path>"

Only report success if the helper succeeds. On FREEZE_BUSY or unexpected state, preserve it and ask the user to inspect recovery after any active writer finishes; never write or delete the state file directly.

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

How it works

The hook reads file_path from the Edit/Write tool input JSON (shared real-JSON extractor with /careful β€” one copy, sourced by both hooks), then checks whether the path starts with the freeze directory. If not, it returns a hookSpecificOutput payload with permissionDecision: "deny" to block the operation (nested under hookSpecificOutput β€” Claude Code ignores a top-level permissionDecision).

Polarity is fail-closed: a tool payload the hook cannot parse is DENIED, not allowed β€” a boundary that fails open is not a boundary. A payload that parses but has no file_path (a non-file tool) is allowed. Symlinks are resolved through their FINAL component, so an in-boundary symlink pointing outside the boundary is checked against its target.

The freeze boundary persists until explicitly removed via the state file. The hook script reads it on every Edit/Write invocation. Boundaries containing spaces are supported.

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; ending or killing a conversation does not remove persisted state

Source: SKILL.md on GitHub

No alerts3d3 checks Β· Risk SAFE
  • Gen Agent Trust Hub3d

    The skill is a developer utility designed to prevent accidental edits by restricting file changes to a specific directory. It uses PreToolUse hooks to intercept and block edit/write operations outside the defined boundary. While it performs local logging and uses dynamic script sourcing for its logic, these actions are transparent, localized to the user's environment, and part of the skill's intended functionality.

  • Socket3d

    No alerts

  • Snyk3d

    Risk: LOW Β· No issues

Signed by skilld at 01593aa. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 17 hours ago.

Activeupdated 5 days ago
What it can do
Runs commands Reads files
version
0.1.0
All 3 allowed tools
BashReadAskUserQuestion
Other metadata
triggers
[
  "freeze edits to directory",
  "lock editing scope",
  "restrict file changes"
]
hooks
{
  "PreToolUse": [
    {
      "matcher": "Edit",
      "hooks": [
        {
          "type": "command",
          "command": "bash $HOME/.claude/skills/gstack/freeze/bin/check-freeze.sh",
          "statusMessage": "Checking freeze boundary..."
        }
      ]
    },
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "command",
          "command": "bash $HOME/.claude/skills/gstack/freeze/bin/check-freeze.sh",
          "statusMessage": "Checking freeze boundary..."
        }
      ]
    }
  ]
}
  • freeze
  • file-editing
  • scope-restriction
  • safety-boundary
  • session-state
  • bash

README badge

README badge for garrytan/gstack/freeze

Blocks Edit and Write operations outside a specified directory for the session, preventing accidental changes to unrelated files. Use when debugging a specific module or when you need to scope all modifications to a single folder.

Generated from the current SKILL.md.

Does this skill prevent all file modifications outside the freeze directory?
No. It blocks the Edit and Write tools specifically. Bash commands like sed or other shell utilities can still modify files outside the boundary, so this is a convenience guard rather than a security boundary.
How do I change or remove the freeze boundary during a session?
Run `/freeze` again to set a new directory, or run `/unfreeze` to remove the restriction. The boundary is also cleared when the session ends.
Does this affect read operations like viewing or searching files?
No. The freeze restriction applies only to Edit and Write tools. Read, Bash, Glob, and Grep operations work anywhere in the repository.
What happens if I try to edit a file outside the freeze directory?
The operation is blocked before it runs. The agent receives a denial response and cannot proceed with that edit.

Generated from the current SKILL.md. These answers refresh after source changes.