legacy-endpoints

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

Updated Aug 23, 2026
Ready to run
npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-endpoints
๐Ÿ’ฌ Prompt for ChatGPT / Claude Chatโ–ผ
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.