Rules and guidelines for working with Spring Data JPA in the project. ALWAYS use this skill when adding, removing, or modifying JPA entities, repositories, or projections. Trigger on any request that involves changing entity structure, adding new entities, modifying field annotations, updating database mappings, creating or modifying Spring Data repositories, or defining query projections (interfaces, DTOs).
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
When the task involves creating or modifying a JPA entity:
references/entity-conventions.md and follow all substeps there to detect project conventions.references/entity-rules-impl.md and follow the rules there when writing or modifying the entityWhen the user asks to review JPA patterns, conventions, or code quality in the project:
references/entity-conventions.md (steps 1.1–1.5).references/entity-rules-impl.md. For each deviation, output a recommendation in the format:### JPA Review
**[Convention or pattern name]**
- Current: <what the project does>
- Recommended: <what the best practice says>
- Reason: <why this matters>If no deviations are found — state that the project follows best practices.
When the task involves adding or modifying transactional behavior:
references/transaction-conventions.md and follow all substeps there to detect project conventions.references/transaction-rules-impl.md and follow the rules there when writing or modifying transactional code.4d8e766
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.