molt-verify

Compare source and target databases for schema and row-level consistency.

18|8|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/cockroachlabs/cockroachdb-skills --skill molt-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: molt-verify
Source: https://github.com/cockroachlabs/cockroachdb-skills/tree/main/skills/onboarding-and-migrations/molt-verify
Command: npx skills add https://github.com/cockroachlabs/cockroachdb-skills --skill molt-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migration teams need a reliable way to verify that a database migration preserves both schema and data integrity across environments.

Core Features & Use Cases

  • Schema verification: checks table presence, columns, types, NOT NULL constraints, and primary key structure to ensure parity between source and target.
  • Row-level data validation: iterates source rows and compares against target to detect missing, extraneous, and mismatched rows per shard.
  • Post-migration validation workflows: coordinates with molt fetch and verify steps to confirm migration success in CI/CD pipelines.

Quick Start

Use molt verify after a migration to confirm that the source and target databases are in sync.

Frequently Asked Questions about molt-verify

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

FAQPage Schema
How do I verify database migration integrity for schema and data consistency?

Verify database migration integrity by comparing source and target databases to detect schema gaps and row-level mismatches. It checks table columns, types, constraints, and iterates rows to find missing or extraneous data per shard.

Does migration verification work with PostgreSQL and Oracle source databases?

Migration verification works with PostgreSQL and Oracle sources targeting CockroachDB. Oracle support requires a CGO build alongside the molt binary and accessible source and target databases to execute validation.

How do I validate large datasets after a database migration without excessive overhead?

Validate large datasets after migration by tuning concurrency, sharding, and selective verification options. These parameters control the row-level iteration process to manage performance overhead when comparing source and target databases.

What schema elements are checked during post-migration database verification?

Post-migration database verification checks table presence, columns, data types, NOT NULL constraints, and primary key structure. This ensures full schema parity between the source and target databases.

Why does database migration verification report extraneous rows in the target database?

Database migration verification reports extraneous rows because the row-level validation iterates source rows and compares them against the target to detect data that exists in the target but not the source.

What do I need to run post-migration verification for CockroachDB targets?

To run post-migration verification for CockroachDB targets, you need the molt binary and accessible source and target databases. Oracle sources additionally require a CGO build for proper connectivity.