guard

Pre-tool hook safety checks prevent accidental data loss by warning and blocking destructive commands like rm -rf or force-push before execution. This mechanism intercepts risky operations during critical development and production tasks to safeguard your systems.

Yes, you can restrict file edits to a specific directory boundary to enforce safe limits during live debugging. By defining a user-specified directory, the safeguard blocks any unauthorized file modifications outside that boundary.

Pre-tool hooks work by running safety checks before tool execution to intercept and block unsafe operations. They coordinate with sibling safety skills to enforce directory boundaries and prevent destructive commands from modifying critical systems.

The best way to enforce safety boundaries is by applying dual protection: issuing warnings for destructive commands and restricting edits to a user-specified directory. This prevents accidental damage in critical production environments and live deployments.

Yes, the edit boundary safeguard works for both development and production tasks that touch critical systems. It restricts file modifications to a safe directory, preventing accidental damage during live deployments and local debugging.