avad-freeze

To restrict edits to a specific directory during a debugging session, this Skill enforces runtime boundary checks using a stateful freeze file and Edit/Write hooks, ensuring only in-scope changes are allowed and persisting the boundary across the session.

Directory freezing locks edits to a user-specified folder to prevent accidental code changes. It establishes a persistent boundary at the start of a session, ensuring repeated modifications remain contained within the intended module without requiring reconfiguration.

Yes, you can lock file modifications to a single module for focused work. By specifying a target directory during setup, the Skill applies an immediate boundary that restricts Edit and Write operations exclusively to that path.

To set up a workflow hook isolating changes to one folder, specify the desired directory to freeze. The setup workflow applies the boundary immediately, utilizing stateful hooks to intercept and validate edits against the frozen scope.

Yes, the edit freeze persists across the entire session without reconfiguration. The Skill uses a stateful freeze file to maintain the boundary, ensuring repeated edits stay contained within the originally specified directory throughout the active session.

If you attempt to write files outside the frozen directory scope, the runtime boundary checks enforced by the Edit and Write hooks will block the operation. This ensures unintended changes are prevented and modifications remain isolated to the in-scope path.