What problem does it solve? Writing JPA Repository classes by hand for every new domain Entity is repetitive boilerplate work, and inconsistencies creep in when teams mix Spring Data JPA interfaces with manual EntityManager implementations. This Skill collects the target Entity, implementation style, and custom query methods through a short interview, then generates a Repository class that matches the project's existing conventions. ## Core Features & Use Cases - Guided Interview: Asks one question at a time to collect the target domain, implementation approach, and required custom query methods, skipping questions when the user already provided enough detail. - Two Implementation Styles: Generates either a Spring Data JPA interface extending JpaRepository with @Query methods, or a manual EntityManager-based @Repository class with find, save, and delete operations. - Convention Enforcement: Keeps PK types as Integer, writes explicit JPQL for join fetches, and places output in the domain package path consistent with the existing codebase. - Use Case: You add a new Board entity to a Spring Boot project and need a repository with a join-fetch query. Ask for the repository, answer two or three questions, and receive a ready-to-use BoardRepository.java. ## Quick Start Ask the assistant to create a repository for your entity, for example by saying "Board 엔티티의 레포지토리 만들어줘" or typing /gen-repository.
