skills.rest
nathangalea
nathangaleaCOMMUNITY
Explore all skills by this author →
GitHub

migration-guide

Analyzes Mercur 1.x projects to plan migration to Mercur 2.0.

Updated May 2, 2026
Search Tags:#automation#refactoring#dependencies#migration#project analysis#upgrade#mercur
One-click install
npx skills add https://github.com/nathangalea/plants-direct --skill migration-guide-nathangalea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-guide
Source: https://github.com/nathangalea/plants-direct/tree/main/.claude/skills/migration-guide
Command: npx skills add https://github.com/nathangalea/plants-direct --skill migration-guide-nathangalea

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and teams analyze their existing Mercur 1.x projects and create a clear migration strategy to Mercur 2.0, reducing manual effort and errors.

Core Features & Use Cases

  • Project Analysis: Automatically scans package dependencies, configuration files, and project structure to assess current setup.
  • Migration Planning: Provides actionable recommendations for module, plugin, and code porting based on project specifics.
  • Use Case: A developer wants to upgrade a complex project with custom modules and workflows; this Skill offers a comprehensive migration plan tailored to their codebase.

Quick Start

Provide the path to your existing Mercur 1.x project as an argument to generate a step-by-step migration plan.

Frequently Asked Questions about migration-guide

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

FAQPage Schema
How do I migrate a Mercur 1.x project to 2.0?▼

To migrate Mercur 1.x projects to 2.0, analyze your codebase to identify dependencies, configuration files, and custom modules, then generate a tailored porting plan. Providing your project path yields step-by-step migration instructions covering modules, workflows, and API routes.

What is checked during a Mercur 2.0 upgrade analysis?▼

A Mercur 2.0 upgrade analysis scans package dependencies, configuration files, and project structure to identify custom code and compatibility issues. It assesses modules, workflows, and API routes to provide actionable porting recommendations tailored to your codebase.

Can I get a custom migration plan for complex Mercur projects with custom modules?▼

Yes, you can generate a custom migration plan for complex Mercur projects with custom modules. The analysis scans your specific codebase, identifying custom workflows and modules to provide comprehensive, tailored porting recommendations for your project structure.

How do I identify compatibility issues before upgrading Mercur dependencies?▼

To identify compatibility issues before upgrading Mercur dependencies, scan your project to assess current setup and configuration files. This analysis automatically performs compatibility checks, highlighting dependencies and custom code that require updates for the new version.

What is the best way to port custom workflows and API routes to Mercur 2.0?▼

The best way to port custom workflows and API routes to Mercur 2.0 is to run an automated project analysis. It identifies your specific custom code and structures, providing tailored porting instructions to ensure full compatibility with the updated framework.

Related Skills

Explore More Software Engineering Skills→
amo-tech-aiamo-tech-ai
2

migration-guide

Guide Mercur 1.x to 2.0 migration with analysis, mapping, and execution.

Community
Advanced
OZVEOZVE

migration-guide

Classify Mercur 1.x projects and guide migration to Mercur 2.0.

Community
Advanced
BigdropsBigdrops
1

gitnexus-refactoring

Automate code refactoring with dependency mapping and dry-run verification.

Community
Advanced
microsoftmicrosoft
19

migrating-newtonsoft-to-system-text-json

Automate .NET project migration from Newtonsoft.Json to System.Text.Json.

Official
Intermediate