skills.rest
ryu-qqq
ryu-qqqCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

legacy-flow

Track and document legacy API call flows from Controllers to the DB.

Updated Aug 27, 2026
Search Tags:#database#traceability#documentation-generation#api-documentation#controller-service-repository#legacy-flow#call-flow
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legacy-flow
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/legacy-flow
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill legacy-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

레거시 API 엔드포인트의 전체 호출 흐름을 추적하고 문서화하여, 개발팀이 엔드포인트 간 의존성과 데이터 흐름을 한 눈에 파악할 수 있도록 합니다. Controller→Service→Repository→DB의 흐름을 명확하게 기록합니다.

Core Features & Use Cases

  • 레거시 엔드포인트의 전체 호출 흐름 자동 추적 및 문서화
  • Controller, Service, Repository 간의 상호 작용 및 데이터 흐름 시각화
  • 출력 대상: claudedocs/legacy-flows/{web|admin}/{Controller}_{method}.md 형식의 문서 생성
  • Use Case: 레거시 API를 분석해 마이그레이션 계획 수립 및 애플리케이션 규칙성 파악에 활용

Quick Start

대상 컨트롤러와 메서드를 지정하여 분석을 실행하고, 결과 문서를 claudedocs/legacy-flows에 생성합니다.

Frequently Asked Questions about legacy-flow

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

FAQPage Schema
How do I trace the full call flow of legacy API endpoints from Controller to DB?▼

To document legacy API call flows end-to-end, track the path from Controller through Service and Repository to the DB, capturing methods, paths, DTOs, and data access patterns to visualize data flow and dependencies.

What is the best way to document legacy API call flows for migration planning?▼

Documenting legacy API call flows for migration involves tracking Controller, Service, and Repository interactions to generate consistent documentation artifacts, helping teams analyze dependencies and establish application rule patterns.

Can I automatically generate API documentation for legacy Controller, Service, and Repository layers?▼

Yes, you can automatically generate API documentation for legacy layers by tracking the interactions between Controller, Service, and Repository components, capturing DTOs and data access patterns to produce end-to-end visibility artifacts.

How do I get started with end-to-end visibility for retroactive API systems?▼

To get end-to-end visibility for retroactive API systems, specify the target controllers and methods for analysis to generate documentation artifacts that capture the full call flow and data access patterns consistently.

What format is used for documenting legacy API call flows and traceability?▼

Legacy API call flow documentation is generated as Markdown files in the claudedocs/legacy-flows directory, organized by web or admin modules and named using the Controller and method conventions for consistent traceability.

Related Skills

Explore More Software Engineering Skills→
ConductionNLConductionNL
1

hydra-gate-orphan-auth

Detect orphaned authorization methods in PHP service and controller classes.

Official
Advanced
DauQuangThanhDauQuangThanh
14

cobol-migration-analyzer

Analyze COBOL programs, JCL jobs, and copybooks to generate a Java migration plan.

Community
Advanced
aws-samplesaws-samples
84

test-database-feature

Run repository integration tests against a real MySQL database with Prisma migrations.

Official
Advanced
involvexinvolvex
1

developer-detective

Trace data flow across call graphs using AST analysis.

Community
Advanced