What problem does it solve? Writing JPA entities, repositories, and transactional code that stays consistent with an existing Spring project's conventions is error-prone: ID strategies, naming templates, Lombok usage, equals/hashCode patterns, and fetch types vary from project to project. This Skill detects the conventions already used in your codebase and enforces best-practice rules so every new or modified entity matches the project style. ## Core Features & Use Cases - Convention Detection: Scans existing entities via Spring MCP tools to score conventions such as ID strategy, sequence scope, naming templates, Lombok usage, and equals/hashCode style, asking the developer only when confidence is low. - Entity Implementation Rules: Applies detailed rules for @Entity classes, @Id generation (SEQUENCE, IDENTITY, UUID), @Column naming, BigDecimal precision/scale, and OneToMany/ManyToOne/ManyToMany mappings. - Safe equals/hashCode and toString: Generates proxy-safe HibernateProxy-based equals/hashCode and toString implementations that avoid LazyInitializationException by excluding relation fields. - JPA Review Mode: Compares detected project conventions against best practices and reports deviations with recommendations. - Use Case: When asked to add a new Loan entity to a Spring Boot project, the Skill inspects existing entities, confirms conventions like SEQUENCE IDs and explicit naming, then generates the entity with correct annotations, Lombok configuration, and proxy-safe equals/hashCode. ## Quick Start Ask the assistant to create a new JPA entity or modify an existing one in your Spring project, and it will detect your project's conventions before writing the code.
