spring-data-jpa

Enforce project-wide Spring Data JPA conventions for entities, repositories, and projections.

106|11|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Amplicode/spring-skills --skill spring-data-jpa-amplicode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spring-data-jpa
Source: https://github.com/Amplicode/spring-skills/tree/main/skills/spring-data-jpa
Command: npx skills add https://github.com/Amplicode/spring-skills --skill spring-data-jpa-amplicode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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).

Core Features & Use Cases

  • Provides project-wide conventions for entity naming, access strategies, validation, and transaction handling.
  • Guides developers through creating and updating JPA artifacts with consistent patterns and checks.
  • Use Case: When adding a new JPA entity or updating mappings, follow these rules to ensure compatibility with existing conventions and tests.

Quick Start

Review the project’s JPA conventions and apply the documented steps before committing any entity, repository, or projection changes.

Frequently Asked Questions about spring-data-jpa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce naming conventions when creating JPA entities and repositories?

To enforce naming conventions for JPA entities and repositories, apply project-wide rules that standardize entity naming, access strategies, and constraint enforcement across all modules. This ensures structural compatibility and consistent database mappings.

What are the best practices for modifying Spring Data JPA mappings safely?

The best practice for modifying Spring Data JPA mappings safely involves validating field annotations and following documented entity rules. This safeguards database mappings by applying consistent patterns and transactional guidance before committing changes.

How do I define query projections using Spring Data JPA?

To define query projections using Spring Data JPA, create interfaces or DTOs that map to specific entity fields. Follow project conventions to ensure these projections integrate safely with existing repository patterns and validation rules.

Does this project provide transaction handling guidance for Spring Data repositories?

Yes, this project provides transaction handling guidance for Spring Data repositories. It codifies project-wide conventions for transactional behavior, ensuring that repository modifications and entity mappings follow consistent, safe execution patterns.

When should I use standardized rules for updating Hibernate entity access strategies?

You should use standardized rules for updating Hibernate entity access strategies whenever you modify field annotations or change entity structure. This ensures compatibility with existing conventions and maintains database mapping integrity across modules.