guard

You can prevent accidental destructive commands in production by activating guard mode, which detects dangerous patterns like rm -rf or DROP TABLE and alerts you before execution. You retain the option to intentionally override the warning if the action is required.

You can restrict file edits to a specific directory scope by setting a configurable edit boundary before debugging live systems. This blocks all file modifications outside your specified directory, preventing unintended changes to unrelated sensitive files.

Directory-scoped edit restriction is a safety mechanism that blocks all file edits outside a user-specified boundary. It protects sensitive project directories by ensuring that any accidental out-of-scope modifications are actively prevented during infrastructure management.

Yes, you can override a destructive command warning if the action is intentional. The guard mechanism alerts you before executing dangerous commands, but it allows authorized overrides to ensure legitimate operational tasks are not blocked during production work.

Yes, this CLI safety tool works without additional dependencies or components. It operates independently to combine destructive command pattern detection with directory-scoped edit restrictions, enforcing operational safety directly within your existing workflow.

You should use guard mode for production safety when debugging live services, managing production infrastructure, or editing sensitive project directories. It enforces maximum operational safety by preventing outages or data loss from unintended modifications.