deployment-verification-agent

To create a pre-deployment checklist for production database changes, define critical data invariants and generate read-only SQL audit queries to verify data integrity before executing migrations. This establishes baseline conditions for safe software releases.

The best way to verify data integrity after a production deployment is to execute read-only SQL verification queries that validate predefined data invariants, ensuring no silent data corruption, loss, or duplication occurred during the release process.

To plan a rollback procedure for a production database migration, outline clear, sequential steps to revert schema and data changes. This ensures you can restore the previous state if post-deployment verification queries detect invariant violations.

You need a formal deployment verification process when a pull request modifies critical database tables or production data, requiring executable pre-deployment checks and post-deployment audits to confidently make a Go/No-Go release decision.

Yes, you can use read-only SQL queries to prevent silent data corruption during releases by auditing data invariants before and after deployment. These queries verify that critical data properties remain intact without modifying the production database.

A production deployment rollback strategy should include specific data invariants to check, post-deployment SQL verification queries to detect anomalies, and clear, executable steps to revert migrations if data integrity checks fail.