freeze

To restrict file edits to a single directory during a debugging session, you can lock edits to a designated folder. This confines changes and prevents accidental modifications to files outside the allowed path.

Preventing accidental file modifications outside your project folder while prototyping requires setting a session boundary. You specify a designated directory, and the system enforces boundaries via a pre-action check script to block external writes.

A pre-action check script enforces filesystem boundaries by validating file paths against a stored session state. If an edit targets a path outside the designated directory, the script intercepts and blocks the modification before it occurs.

Yes, you can confine code changes to one folder without modifying your entire repository structure. By setting an allowed directory path for the current session, the enforcement mechanism scopes all writes exclusively to that target folder.

Yes, you need to manually specify the allowed directory path each time you start a focused development session. The skill requires an interactive prompt to set the allowed directory and stores this boundary in the session state for active enforcement.

Use a session boundary to lock filesystem edits when actively debugging or investigating a specific module. It provides immediate, hard enforcement against accidental writes during the session, complementing standard version control which only tracks changes after the fact.