deployment-verification-agent

Generate deployment verification checklists with SQL queries and rollback steps.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/CristoVentures/LocalCents --skill deployment-verification-agent-cristoventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-verification-agent
Source: https://github.com/CristoVentures/LocalCents/tree/main/.agent/skills/deployment-verification-agent
Command: npx skills add https://github.com/CristoVentures/LocalCents --skill deployment-verification-agent-cristoventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployment changes that touch production data can introduce data integrity issues, regressions, or downtime if verification is skipped or improvised. This Skill provides a repeatable framework to generate concrete, executable deployment verification checklists that validate invariants, verify data state before/after deployment, and codify rollback and monitoring plans.

Core Features & Use Cases

  • Identify data invariants and generate read-only verification SQL queries to prove correctness.
  • Document destructive steps, rollback behavior, and safe backfill strategies.
  • Produce Go/No-Go checklists that guide engineers through pre/post deploy validation and monitoring.

Quick Start

Create a concrete deployment verification checklist for a PR that touches production data and requires a Go/No-Go decision.

Frequently Asked Questions about deployment-verification-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Go/No-Go deployment checklist for a data migration?

A deployment verification checklist for production data changes details data invariants, read-only verification SQLs, rollback behavior, and post-deploy monitoring plans. It guides engineers through pre/post validation to prevent data integrity issues, regressions, or downtime during schema changes and backfills.

How do I verify data invariants before and after a schema change?

You verify data invariants by running read-only verification SQL queries that prove data correctness before and after deployment. The checklist framework identifies these invariants and provides the executable SQL needed to validate data state during schema changes, migrations, and backfills.

What should a rollback plan include for destructive database migrations?

A rollback plan for destructive database migrations should document the destructive steps, outline rollback behavior, and establish safe backfill strategies. This ensures you can restore data integrity if production deployment verification fails or invariants are violated.

When do I need a deployment verification checklist for production data?

You need a deployment verification checklist when a PR touches production data and requires a Go/No-Go decision, such as data migrations, backfills, or schema changes. It provides a repeatable framework to validate invariants and prevent data integrity issues, regressions, or downtime.

How do I set up post-deploy monitoring after a data backfill?

You set up post-deploy monitoring after a data backfill by prescribing monitoring plans within your deployment verification checklist. This tracks the data invariants and verification queries established pre-deploy to ensure ongoing data correctness, system stability, and early detection of regressions.