migration-validate

Validate migration completeness and version drift against workflow standards.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill migration-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-validate
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/migration-validate
Command: npx skills add https://github.com/oogDZ/2 --skill migration-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate migration completeness by checking version drift, alignment with workflow standards, and the freshness of scripts. Use after /migration-create to confirm all dependencies are synchronized.

Core Features & Use Cases

  • Ensures SSOT alignment for migrations and current repository state.
  • Verifies drift, standard adherence, and script relevancy across workflows.
  • Use Case: a release team runs /migration-validate after creating migrations to confirm all dependencies are in sync before deployment.

Quick Start

Run /migration-validate [standard] to verify migration completeness against the selected standard.

Frequently Asked Questions about migration-validate

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

FAQPage Schema
How do I validate migration completeness and check for version drift?

To validate migration completeness, run a validation process against your selected standards to check version drift, workflow standard adherence, and script freshness. This confirms that all dependencies are synchronized across workflows and scripts before deployment.

When do I need to run a migration validation check?

You need to run a migration validation check immediately after creating migrations to confirm all dependencies are in sync. Release teams use it to verify version drift and workflow standard adherence before proceeding with deployment.

How do I verify workflow standard adherence and script freshness after a migration?

You verify workflow standard adherence by running a validation command with the target standard as a parameter. This checks your repository state for SSOT alignment, ensuring scripts are up-to-date and dependencies synchronize correctly across workflows.

Can I use migration validation to ensure dependencies are synchronized across workflows?

Yes, migration validation ensures dependencies are synchronized across workflows and scripts. It identifies version drift and checks repository state alignment against single source of truth standards to confirm completeness before deployment.

What is the best way to confirm repository state alignment before deployment?

The best way to confirm repository state alignment is to validate migration completeness against selected standards. This process verifies version drift, workflow standard adherence, and script relevancy to ensure full SSOT alignment before deployment.