guard-mode

To prevent destructive commands in a shared repository, you need a safety mode that warns before executing actions like rm -rf or DROP TABLE. This skill intercepts these operations and requires explicit user confirmation to proceed.

Yes, you can lock edits to a specific directory by providing a directory path. The session will then block any file modifications outside that specified directory boundary to prevent catastrophic changes.

To add git safety warnings before force-pushing to main or using amend, you need a guard mode that detects these operations. It warns you and provides guidance on how to revert the changes when possible.

The best way to ensure explicit warnings and override prompts is to activate a guard mode that monitors session commands. It halts destructive actions and requires explicit user consent before proceeding.

Yes, guard mode provides session deactivation controls and enforces directory boundaries. You can restrict edits to one directory and override the freeze with confirmation prompts when critical operations are needed.

You should not use directory freeze when you need to perform widespread edits across multiple directories in a session. It blocks edits outside the specified directory, requiring manual override prompts for each external change.