Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →decebals/jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries).
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We are configuring Flyway in a Spring Boot application to manage database schema migrations. Migration scripts are stored in db/migration. What naming convention must SQL migration files follow (for example, version 1.1 adding a user table) so Flyway executes them in sequence?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends file naming format starting with V1_1__ followed by description | Missed | Passed |
| Does not recommend JPA entity annotations or JPQL fetch joins | Passed | Passed |
The instructions your model reads when the skill loads.
Best practices and common pitfalls for JPA/Hibernate in Spring applications.
| Problem | Symptom | Solution |
|---|---|---|
| N+1 queries | Many SELECT statements | JOIN FETCH, @EntityGraph |
| LazyInitializationException | Error outside transaction | Open Session in View, DTO projection, JOIN FETCH |
| Slow queries | Performance issues | Pagination, projections, indexes |
| Dirty checking overhead | Slow updates | Read-only transactions, DTOs |
| Lost updates | Concurrent modifications | Optimistic locking (@Version) |
The #1 JPA performance killer
// ❌ BAD: N+1 queries
@Entity
public class Author {
@Id private Long id;
private String name;
@OneToMany(mappedBy = "author", fetch = FetchType.LAZY)
test cases passed, vs 21 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.