springboot-repository-service

Provide the existing JPA entity, the desired operations, and the read records the service should return. The skill generates a JpaRepository interface with derived methods or @Query text blocks, plus a @Service class with constructor injection and transactional methods.

Use join fetch in @Query whenever a query returns an entity and accesses one of its @ManyToOne associations. Without it, each returned row triggers an extra query. The skill applies this invariant automatically in every custom query it writes.

A service should never return the JPA entity outside its module; it should map results to a Java record before returning. Returning entities risks lazy-loading exceptions outside transactions and couples upper layers to the domain model.

Yes, if the target project already uses Lombok, the skill mirrors that house style and declares the divergence. The invariant is constructor-based injection itself, not the absence of Lombok, and other rules like join fetch and readOnly transactions still apply.

Tests use @SpringBootTest gated by @EnabledIfEnvironmentVariable with DB_URL, so they run against a real Postgres only when the variable is set. A plain mvn test without the database skips them with a declared SKIP rather than a fake pass.

Do not use it before the entity and its columns exist, since generation without the confirmed entity is blocked. For entity and migration creation use the entity skill, and for controllers or Thymeleaf screens use the controller skill instead.