What problem does it solve? When debugging or working in a large codebase, AI-assisted edits can accidentally modify unrelated files outside the intended scope. This Skill enforces a hard boundary so that Edit and Write operations targeting files outside a chosen directory are blocked, not just warned about. ## Core Features & Use Cases - Edit Boundary Enforcement: A PreToolUse hook intercepts every Edit and Write call and denies any operation whose file path falls outside the frozen directory. - Session-Persistent State: The freeze boundary is stored in a state file (~/.gstack/freeze-dir.txt) and persists for the entire session until removed with /unfreeze. - Path Safety Handling: Trailing-slash normalization prevents sibling directories like /src-old from matching a /src boundary, and relative paths are resolved to absolute before checking. - Use Case: While debugging a failing module in src/payments, freeze edits to that directory so the AI cannot accidentally "fix" unrelated code elsewhere in the repository. ## Quick Start Ask the AI to freeze edits to the directory you are working in, for example by saying "freeze edits to src/payments", and confirm the path when prompted.