migrate

Coordinate multi-repo dependency migrations from planning to approved execution.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Conava/claude-devline --skill migrate-conava
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/Conava/claude-devline/tree/main/skills/migrate
Command: npx skills add https://github.com/Conava/claude-devline --skill migrate-conava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates complex dependency migrations across one or many repositories. It coordinates research, planning, and execution using dedicated migration agents to reduce manual work and prevent breaking changes.

Core Features & Use Cases

  • Research migration guides and tooling to plan changes safely across multiple repos.
  • Parse input to identify package, current and target versions, and affected repositories with optional filters.
  • Present a detailed migration plan for user approval before any code changes and agent execution.
  • Coordinate multi-repo migrations via agents with validation, verification, and rollback considerations.

Quick Start

Provide the package name and target version (with optional --repos filters) to generate a migration plan, review the plan, and approve to launch the agents.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I coordinate major dependency upgrades across multiple repositories?

You can automate major dependency migrations across multiple repositories by providing the package name, target version, and optional repository filters. The Skill generates a detailed migration plan for user approval before coordinating execution agents.

What is the safest way to plan major-version migrations for libraries?

Planning major-version migrations safely involves researching migration guides, selecting appropriate tooling, and assessing risks before execution. This approach requires user approval of a detailed migration plan before any agents run.

Can I use this to replace a library or handle EOL dependencies?

Yes, you can use this to handle library replacements and EOL migrations. It orchestrates the entire process from discovery to approved execution, applying dedicated migration agents to prevent breaking changes across affected repositories.

Does the agent execute code changes automatically during a dependency migration?

No, the agent does not execute code changes automatically. It must present a detailed migration plan for explicit user approval before any code changes or agent execution begins, ensuring governance compliance.

How do I start a multi-repo dependency migration?

To start a multi-repo dependency migration, provide the package name and target version with optional --repos filters. The system parses the input, identifies affected repositories, and generates a plan for review before agent execution.