What problem does it solve? After migrating data to CockroachDB with molt fetch, you need proof that the target database actually matches the source — missing rows, mismatched values, or schema drift can silently corrupt a cutover. This Skill guides you through running molt verify to confirm schema and data integrity before going live. ## Core Features & Use Cases - Schema and Row Verification: Compares table presence, columns, types, constraints, and primary keys, then iterates source rows in PK order to detect missing, extraneous, and mismatched rows. - Concurrency and Sharding Tuning: Parallelize verification across tables and within large tables using PK-range sharding, batch sizing, and rate limiting to control production impact. - Schema-Only CI Gates: Run fast DDL-only checks with --rows=false and --non-interactive for automated pipelines. - Use Case: After migrating a PostgreSQL database to CockroachDB, run a full verify with table filters and column exclusions, review per-shard mismatch reports, and fix discrepancies before cutover. ## Quick Start Ask the AI to run molt verify against your source PostgreSQL database and target CockroachDB cluster to confirm the migration copied all rows correctly.