legacy-query

Generate Composite Pattern QueryDSL repositories from legacy-flow analysis documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

legacy-flow 분석 결과를 기반으로 Composite 패턴의 QueryDSL Repository를 자동으로 생성하여, 레거시 시스템의 데이터 액세스 계층을 빠르게 현대화합니다.

Core Features & Use Cases

  • Domain Layer DTOs 및 검색 조건 구성요소를 자동 생성합니다.
  • Application Layer 결과 DTO와 Persistence Layer의 Composite Repository를 함께 생성합니다.
  • Use Case: 레거시 흐름 문서를 바탕으로 Domain/Application/Adapter 계층이 포함된 저장소 구조를 즉시 구성합니다.

Quick Start

Invoke /legacy-query admin:BrandController.fetchBrands to generate the Domain, Application, and Persistence modules.

Frequently Asked Questions about legacy-query

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

FAQPage Schema
How do I generate QueryDSL repositories from legacy Java code?

To generate QueryDSL repositories from legacy Java code, you need a /legacy-flow analysis document, which this tool uses to automatically produce Composite Pattern persistence layer artifacts across Domain, Application, and Persistence modules.

What is the Composite Pattern for QueryDSL repository persistence layers?

The Composite Pattern for QueryDSL repository persistence layers structures data access by generating Domain DTOs, Application result DTOs, and Persistence layer repositories together, allowing layered querying based on legacy-flow analysis outputs.

How do I modernize a legacy persistence layer using domain-driven design?

Modernize a legacy persistence layer using domain-driven design by running /legacy-query on your legacy-flow analysis document to auto-generate structured Domain, Application, and Persistence repository components for your Java project.

Do I need a legacy-flow analysis document to generate repository code?

Yes, you need a legacy-flow analysis document to generate repository code, as the tool requires this analysis output to accurately produce the Domain, Application, and Persistence layer QueryDSL artifacts.

How do I auto-generate Domain and Application DTOs for a Java persistence layer?

Auto-generate Domain and Application DTOs for a Java persistence layer by invoking /legacy-query with your analyzed legacy flow, which creates the required DTOs and search condition components alongside the Composite Repository.

What are the limitations of auto-generating QueryDSL repositories from legacy flows?

Limitations of auto-generating QueryDSL repositories from legacy flows include the strict dependency on having a pre-existing /legacy-flow analysis document, meaning the tool cannot infer repository structures without this prior analysis input.