legacy-migrate

Automate six-step migration of legacy APIs to modular admin and web services.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-migrate
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/legacy-migrate
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

레거시 API를 새 아키텍처로 완전 마이그레이션하는 자동화 워크플로우로, 반복 작업을 줄이고 마이그레이션 시간과 리소스 낭비를 최소화합니다.

Core Features & Use Cases

  • 엔드포인트 분석에서부터 DTO 변환, 지속 계층 생성, 애플리케이션 계층 구성, 컨트롤러 생성에 이르는 6단계 워크플로우를 순차적으로 실행합니다.
  • 모듈 간 경계(Admin, Web 등)에서 재사용 가능한 마이그레이션 컴포넌트를 생성하고, 각 단계의 산출물을 다음 단계로 안전하게 전달합니다.
  • 실패 시 자동 재개 포인트 지정(--step 옵션) 및 명확한 로그/보고서를 제공합니다.

Quick Start

Legacy migrate 워크플로우를 시작하려면 대상 모듈과 필요한 시작 단계 옵션을 포함하여 명령을 실행합니다.

Frequently Asked Questions about legacy-migrate

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

FAQPage Schema
How do I automate legacy API migration to a modern architecture?

Automating legacy API migration involves a six-step sequential workflow that analyzes endpoints, generates DTOs, creates persistence layers, configures application services, and generates controllers to move legacy APIs to a modern modular architecture.

What is the best way to migrate multi-module legacy services involving endpoints and DTOs?

The best way to migrate multi-module legacy services is using an automated workflow that sequentially processes endpoints, DTOs, persistence, service, and controller generation while maintaining clear boundaries across Admin and Web modules.

Can I resume a legacy API migration workflow from a specific step if it fails?

Yes, you can resume a failed legacy API migration workflow from a specific step by using the --step option to re-enter the sequential workflow at the desired point without restarting the entire process.

Does the automated migration workflow support code generation for persistence and service layers?

Yes, the automated migration workflow supports code generation for persistence and service layers, systematically creating DTOs, persistence components, application service configurations, and controllers during the sequential six-step process.

How are migration errors handled when moving legacy APIs to a new architecture?

Migration errors are handled through comprehensive error reporting and clear logs, allowing users to safely pass artifacts between steps and automatically resume the workflow from the exact failure point using the step re-entry option.