wizard

To require human approval before destructive git pushes or database migrations, enforce step-by-step gates that announce intent, list impact, provide rollback instructions, and wait for explicit consent before executing. This prevents accidental irreversible changes and data loss.

A human-in-the-loop approval gate for destructive operations is a safety mechanism that halts automated workflows to present impact details and rollback steps, capturing explicit operator consent before executing irreversible actions like file deletions or infrastructure updates.

To safely execute a production database migration, enumerate affected tables and rows, present rollback commands, and require an authorized approval confirmation before proceeding. The workflow halts on failures for operator review and provides immediate post-action confirmations.

Yes, the approval gate workflow applies to force git pushes, infrastructure updates, file system operations, dependency removal, and database schema changes, grouping related small changes into a single gate while avoiding batching unrelated destructive actions.

You should not use automated batching for destructive file system operations when the actions are unrelated, as the safety-first workflow groups related small changes into a single gate but explicitly avoids batching unrelated destructive actions to ensure proper operator review.