destructive-change-guard

To prevent accidental data loss, you can enforce gated safety checks for destructive changes. This requires AI agents to stop and assess recovery readiness before executing medium or high-risk operations like deletes, resets, or bulk replacements.

A recovery gate is a structured safety checkpoint that classifies risk, recoverability, and scope before executing destructive git operations. It ensures recovery readiness is verified for medium and high-risk changes, preventing irreversible information loss.

Risk classification involves assessing the target, change type, information-loss potential, and scope of bulk replacements or rollbacks. Medium and high-risk documentation changes require passing a structured recovery gate before execution.

Yes, the stop-first safety rule immediately halts never-auto-execute patterns like rm -rf, git reset --hard, and git clean. This prevents accidental removal of user-owned information by requiring manual confirmation before proceeding.

Yes, light and strong protection modes allow a fast path for clearly low-risk, tightly scoped changes while enforcing a full gated workflow with recovery templates for medium and high-risk destructive work.

Automated change control for scope-unclear cleanups requires halting execution immediately. Operations lacking clear scope cannot auto-execute and must pass structured risk assessment and recovery readiness checks to prevent data loss.