migrate

Analyze ScalarDB setups and generate migration plans for interface and API transitions.

12|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/wfukatsu/nexus-architect --skill migrate-wfukatsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/migrate
Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill migrate-wfukatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill serves as a migration advisor for ScalarDB interface combinations, guiding Core<->Cluster, CRUD<->JDBC, and 1PC<->2PC migrations.

Core Features & Use Cases

  • Interface Migration Analysis: Identifies the current state of ScalarDB setups, such as deployment, API, and transaction modes.
  • API Migrations: Supports CRUD to JDBC/SQL and vice versa, enhancing SQL capabilities.
  • Transaction Mode Migrations: Manages 1PC to 2PC migrations for distributed transactions.

Quick Start

Analyze the migration plan for converting your current Core CRUD 1PC setup to a Cluster CRUD 1PC setup using the '/scalardb:migrate' command.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I migrate ScalarDB from a Core to a Cluster setup?

Migrating ScalarDB from Core to Cluster requires a structured interface migration plan that analyzes your current deployment state and outlines the necessary configuration changes. This Skill provides that exact transition analysis.

Can I migrate ScalarDB from CRUD to JDBC for SQL capabilities?

Yes, you can migrate ScalarDB from CRUD to JDBC or SQL to enhance your SQL capabilities. This Skill serves as an advisor to identify your current API state and map out the required code modifications for the transition.

What is the best way to transition ScalarDB transaction modes from 1PC to 2PC?

The best way to transition ScalarDB transaction modes from 1PC to 2PC is to use a migration advisor that analyzes your current setup and provides a structured plan for managing distributed transactions. This Skill handles that specific transaction mode migration.

Does ScalarDB interface migration support both API and deployment reconfiguration?

Yes, ScalarDB interface migration supports both API reconfiguration, such as CRUD to JDBC, and deployment changes, such as Core to Cluster. The Skill analyzes your current deployment, API, and transaction modes to provide a comprehensive migration plan.

What are the limitations of using an automated ScalarDB migration advisor?

The ScalarDB migration advisor focuses primarily on interface transformations for improved performance and reliability, meaning it provides analysis and a structured plan rather than executing the configuration changes and code modifications automatically.