guard

To prevent accidental destructive commands during production debugging, you can activate a safety mode that warns before executing patterns like rm -rf, DROP TABLE, and force-push attempts. This mode uses hook-based prechecks to intercept and alert you before risky commands run.

The best way to enforce a strict edit boundary for a specific directory path is to use a directory freeze validation script. This blocks file edits outside your selected path, ensuring changes remain scoped to the chosen directory and reducing unintended modifications.

You manually activate guard mode for high-risk coding changes by instructing your agent to run the manual trigger command. This loads sibling careful and freeze validation scripts to apply allowed tools and hook-based prechecks for your sensitive maintenance tasks.

Yes, guard mode works without pre-existing dependencies or external components. It operates by loading internal sibling careful and freeze validation scripts, applying hook-based prechecks and directory-scoped edit enforcement directly within your agent environment.

You should not use a directory freeze boundary when your sensitive development tasks require editing files across multiple directories outside a single path. The strict edit enforcement blocks out-of-scope file edits, which will halt workflows needing broader repository access.