legacy-endpoints

Classify legacy module endpoints into Query and Command and generate documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

레거시 모듈의 엔드포인트를 Query(조회)와 Command(명령)로 분류하고 문서화하여 마이그레이션 계획 수립의 첫 단계를 빠르게 돕습니다.

Core Features & Use Cases

  • 엔드포인트 분류: 엔드포인트를 Query와 Command로 구분하고 관련 메타데이터를 문서화합니다.
  • 자동 문서화: 각 모듈의 엔드포인트를 claudedocs 형식으로 저장합니다.
  • 마이그레이션 로드맵: 모듈별 마이그레이션 순서와 우선순위를 제시합니다.

Quick Start

분석할 엔드포인트를 지정하고 명령을 실행해 자동으로 엔드포인트 문서를 생성합니다.

Frequently Asked Questions about legacy-endpoints

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

FAQPage Schema
How do I classify legacy API endpoints for migration planning?

You classify legacy API endpoints by separating them into Query and Command categories and documenting their metadata. This process generates structured Markdown files to establish a clear migration roadmap for legacy modules.

How do I document legacy module endpoints automatically?

Document legacy module endpoints automatically by running a specified command that analyzes the target modules. It generates per-module Markdown files organized under the claudedocs directory for both web and admin API layers.

What is the best way to separate Query and Command endpoints in a legacy API?

The best way to separate Query and Command endpoints is to analyze each legacy route and categorize it by its operation type. This distinguishes read operations from data mutations to build a structured migration plan.

Can I generate migration documentation for specific admin and web API modules?

Yes, you can generate migration documentation for specific admin and web API modules. The process supports per-module endpoint documentation, creating separate Markdown files for each module within the admin and web directories.

Do I need any external dependencies to document legacy endpoints?

No external dependencies are required to document legacy endpoints. The process operates independently to analyze legacy API modules and output Markdown documentation without requiring additional components.