migration-validate

Validate migration readiness by detecting version drift and script conformity.

31|5|Updated Jan 14, 2026

Search Tags:#validation #dependencies #migration #standards #drift #scripts #workflows

Ready to run

npx skills add https://github.com/NSEvteev/FullSpec --skill migration-validate-nsevteev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration-validate
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/migration-validate
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill migration-validate-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Эта валидация обеспечивает завершённость миграции: выявление дрейфа версий, несоответствия между содержимым рабочих процессов и установленными стандартами, а также актуальность скриптов. Используется после /migration-create для подтверждения что все зависимости синхронизированы.

Core Features & Use Cases

Проверка дрейфа версий миграций и соответствия рабочих процессов стандартам.
Валидация актуальности скриптов и синхронизации зависимостей между миграциями.
Применение в CI/CD и миграционных рабочих процессах для соблюдения SSOT.

Quick Start

Запустите миграцию через /migration-create и затем выполните /migration-validate, чтобы подтвердить синхронность зависимостей и соответствие стандартам.

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 readiness and detect version drift in my repository?▼

To validate migration readiness, you need to detect version drift by reading standard guidelines and migration scripts to verify dependencies are synchronized. This ensures workflows and scripts align with established standards before completing the migration.

What is the best way to check if CI/CD workflows conform to migration standards?▼

Checking CI/CD workflow conformity involves scanning scripts and workflows against standard guidelines to verify alignment. This process confirms that migrated content stays compliant and dependencies remain synchronized across projects.

How do I ensure dependencies are synchronized after a repository migration?▼

To ensure dependencies are synchronized after a repository migration, run validation checks that read migration scripts and standard guidelines. This verifies that all dependencies are current and that migrated content remains compliant with the SSOT.

Can I use migration validation scripts to check for version drift across multiple projects?▼

Yes, migration validation scripts can check for version drift across multiple projects by applying drift checks and standard conformity rules. This verifies script currency and ensures dependencies are synchronized throughout your CI/CD workflows.

Why does my CI/CD workflow validation fail after migrating repository content?▼

Workflow validation fails after migrating repository content when migrated scripts and workflows drift from the established standard. Validation detects this version drift and confirms whether dependencies remain synchronized and compliant with the standard.

Do I need to run a migration creation step before validating dependency synchronization?▼

Yes, you need to run the migration creation step first to generate the migration scripts. Validation then reads these scripts to confirm dependency synchronization, detect version drift, and ensure workflows align with the standard.