gstack-freeze

To block accidental edits outside a specific directory during debugging, you need a session-wide edit boundary that restricts all Edit and Write tool actions to files under a single allowed path, preventing modifications to the rest of the repository.

A PreToolUse permission check for scoped refactoring is a pre-execution hook that inspects each Edit or Write request's target file path and denies any operation attempting to modify files outside a user-defined directory boundary.

To freeze edits to one directory while fixing a module, run the command to set your desired directory path, then ask the AI to make changes. Any attempted edits outside that boundary will be blocked for the duration of the session.

Yes, you can restrict Write tool operations to a single module during scoped maintenance by enforcing a directory boundary. This ensures only the intended folder is modified while the rest of the repository remains untouched.

Yes, edit blocking works for both Edit and Write operations across the entire session by applying a PreToolUse enforcement hook that checks target file paths against persisted session state and denies boundary-violating requests.