guard

To block destructive commands during live debugging, you need a safety mode that warns on risky operations like force-push or DROP TABLE. This skill enforces those safety rails by intercepting dangerous commands before they execute.

Yes, you can restrict file edits to a specific directory in production by defining a runtime boundary. This skill prompts for a target directory and actively blocks any unintended edits outside that defined scope.

Directory-bound edit protection is a safety mechanism that restricts file modifications to a predefined path. It works by establishing a runtime boundary that checks edits against your specified directory and blocks any changes outside it.

To set up guard mode for development workflows, specify the directory you want to restrict edits to. Once the directory is defined, the safety rails activate automatically to warn on destructive commands and enforce the boundary.

Yes, this safety mode works with database operations by warning on destructive commands like DROP TABLE. It applies to development, production, and debugging workflows to prevent risky operations from running unchecked.