guard

Preventing destructive commands during production debugging requires safety mode warnings for actions like rm -rf or DROP TABLE before execution. This mechanism intercepts risky inputs and enforces directory-scoped edit boundaries to restrict changes.

Directory-scoped edit restriction protects live environments by enforcing a boundary that limits modifications to a user-specified directory. This prevents accidental file changes outside the defined scope during sensitive high-risk deployments or live debugging sessions.

Setting up edit boundaries and destructive-command warnings for high-risk deployments involves using interactive setup prompts to select a target directory. This establishes a freeze boundary and activates dual protections against risky actions.

Yes, full safety mode depends on sibling /careful and /freeze skills for setup and validation. It combines their destructive-command warnings and directory-scoped edit restrictions to provide comprehensive dependency-aware integration during critical operations.

The limitation of edit-boundary enforcement for prod debugging is that it restricts edits strictly to a user-specified directory. Operations requiring cross-directory modifications or force-pushes outside the freeze boundary will be blocked by the safety constraints.