freeze

You can prevent accidental edits by applying a freeze boundary that restricts write and edit actions to a user-specified directory. This constraint persists for the session via hooks and a state file, blocking any modifications outside the allowed path.

Yes, you can restrict write access to a single module by setting a specified directory as the active boundary. The skill enforces this scope throughout the session, denying edit and write actions that target files outside that chosen folder.

Directory-bound editing is a safeguard mechanism that quarantines changes to a single folder, preventing drift. It enforces a persisted boundary using hooks and a state file to deny edit and write actions outside the allowed path during development workflows.

You set up a persistent scope by specifying a directory path to restrict edits to, which applies the freeze boundary. The boundary persists for the session via a state file and can be updated with a new path if your target directory changes.

You update the directory path for an active edit boundary by specifying a new target directory during the session. The skill applies the updated freeze boundary immediately, persisting the new path in the state file to allow edits in the newly chosen folder.

Use a folder-level write block when you need to quarantine changes to a single module during debugging and prevent accidental modifications outside that scope. It serves as a persisted safeguard against edit collisions, complementing standard version control practices.