Use when designing or implementing Spring Data JPA on Spring Boot 4 — repository boundaries, projections, query patterns, custom repositories, CQRS read models, entity relationships, or persistence performance fixes. Not for generic SQL help, database admin work, or project-wide migration (see the springboot-migration skill).
88
85%
Does it follow best practices?
Impact
91%
1.04xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Enrollment CQRS and relationship design
Explicit join entity
100%
100%
Enrollment attributes present
100%
100%
Package-private repository
0%
0%
Public query service
100%
100%
JdbcTemplate in query service
100%
70%
View models as Records
100%
100%
Class-level readOnly transaction
100%
100%
ID-based cross-context references
100%
100%
No @OneToMany on parent
100%
100%
LAZY fetch on associations
100%
100%
PageImpl for pagination
100%
100%
No bidirectional @OneToOne
100%
100%
SOLUTION.md structure
100%
100%
Order persistence read-side with projections and JOIN FETCH
Aggregate root repositories only
100%
100%
@Query for multi-filter search
100%
100%
Projection for dashboard
100%
100%
Java Record projection type
0%
100%
LEFT JOIN FETCH usage
0%
0%
DISTINCT with JOIN FETCH
0%
0%
@Param binding
100%
100%
Text blocks in @Query
100%
100%
@Transactional(readOnly=true)
100%
100%
FetchType.LAZY on @ManyToOne/@OneToOne
100%
100%
Flat record + service assembly for nested projection
33%
100%
Structured SOLUTION.md
100%
100%
Spring Data JPA product catalog: dynamic search, bulk ops, batch import
Repository Impl naming
100%
100%
No derived method for search
100%
100%
@Modifying on bulk update
100%
100%
@Transactional on bulk service call
100%
100%
Hibernate batch_size configured
100%
100%
order_inserts enabled
100%
100%
order_updates enabled
100%
100%
SEQUENCE ID strategy
100%
100%
Flush+clear in batch import loop
100%
100%
Projection for search results
100%
100%
Java Record for projection
100%
100%
readOnly transaction on reads
100%
100%
Correct Hibernate 6+ SQL logger
100%
100%
6277c14
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.