validate-migration

Validate Oracle-to-Cosmos DB migrations for schema completeness, data integrity, and change feed processors.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hariinfo/agentic-code-template --skill validate-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-migration
Source: https://github.com/hariinfo/agentic-code-template/tree/main/.claude/skills/migration-validator
Command: npx skills add https://github.com/hariinfo/agentic-code-template --skill validate-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive validation of an Oracle-to-Cosmos DB migration to detect schema gaps, data loss, and processing gaps before or after go-live.

Core Features & Use Cases

  • Schema completeness validation across Oracle tables, columns, and constraints with explicit mappings to Cosmos DB documents.
  • Data integrity checks including row counts, sample records, and embedded documents for denormalized structures.
  • Change feed processor validation and end-to-end verification for Azure Functions replacing Oracle triggers.
  • Pre-flight and post-migration verification workflows with actionable remediation guidance.

Quick Start

Run a full migration validation against the Oracle source and Cosmos DB target to confirm schema, data integrity, and change-feed processing behaves as intended.

Frequently Asked Questions about validate-migration

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

FAQPage Schema
How do I validate data integrity after an Oracle to Cosmos DB migration?

Schema completeness validation maps Oracle tables, columns, and constraints explicitly to Cosmos DB documents. This ensures every relational schema element is accounted for and correctly transformed into the document model.

Does Cosmos DB change feed processor validation cover Oracle triggers replacement?

Migration validation requires modernization-output artifacts including schema-analysis.md, oracle-inventory.json, document-model.md, cosmos-config.json, and a migration subdirectory. These files provide the source schema, inventory, and target configuration needed for checks.

What is the best way to run pre-flight checks for an Oracle to Cosmos DB migration?

Access pattern validation verifies that Cosmos DB queries align with the migrated document model and partition keys. It ensures the NoSQL access patterns are valid and performant compared to the original Oracle query structures.

Why is my Oracle to Cosmos DB migration missing schema constraints?

Missing schema constraints occur when Oracle table constraints are not explicitly mapped to Cosmos DB documents during migration. The schema completeness validation identifies these gaps and provides actionable remediation guidance to fix them.