SkillsAdd

amplicode/spring-skills

spring-data-jpa

Rules and guidelines for working with Spring Data JPA in the project.

First seen Apr 28, 2026

Installation

$ npx skills add amplicode/spring-skills --skill spring-data-jpa
View on skills.sh ↗ GitHub repository ↗

Summary

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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-database-setup Shared topics
prisma/skills

Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, Mon…

269.8K installs
prisma-postgres Shared topics
prisma/skills

Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, an…

263K installs
prisma-driver-adapter-implementation Shared topics
prisma/skills

Required reference for Prisma ORM 7 SQL driver adapter work.

258.3K installs
prisma-upgrade-v7 Shared topics
prisma/skills

Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes.

258.1K installs
prisma-compute Shared topics
prisma/skills

Prisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `pr…

253.4K installs

Also in this package

Other skills from amplicode/spring-skills · top by installs.

npx skills add amplicode/spring-skills
spring-security-configuration 321 spring-planning 321 spring-explore 320 dto-creator 311 mapper-creator 309 java-debug 306 crud-rest-controller 304 spring-data-jdbc 287 kafka-configuration 233 connekt-script-writer 233

Browse all from amplicode/spring-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 112
Default branch main
Open issues 2
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,390 B
  • docs SUMMARY.md 3,353 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 318 installs

SKILL.md

Preflight: Spring MCP

This skill is part of the Spring Agent Toolkit and is designed to work with the Spring MCP server (provided by the Amplicode IntelliJ plugin). Before doing anything else, check your tool list for any Spring MCP tool — they are exposed under the amplicode MCP server (e.g. getprojectsummary, listmoduledependencies, getentitydetails); harnesses that flatten MCP tools into the tool list use the mcpamplicode prefix on the same names.

  • If at least one Amplicode tool is available — MCP is connected. Proceed with the skill below.
  • If none are available — stop and invoke the amplicode-install skill (bundled with the Spring Agent Toolkit). It installs the Amplicode plugin and walks the user through the «Настроить Spring Agent» welcome-screen button + MCP-client restart. After it completes, the MCP tools become available — resume this skill.
  • If amplicode-install is not registered in your skill list, tell the user (in their language): "This skill needs the Amplicode IntelliJ plugin and its MCP server. Install it from https://amplicode.ru/marketplace into IntelliJ IDEA Ultimate/Community or GigaIDE, open any project, click «Настроить Spring Agent» on the Amplicode welcome screen, then restart your MCP client."

Working with JPA Entities

When the task involves creating or modifying a JPA entity:

  1. If entity conventions have not been detected yet in this conversation — check memory for previously saved conventions first. If found in memory, reuse them. Otherwise read references/entity-conventions.md and follow all substeps there to detect project conventions.
  2. Read references/entity-rules-impl.md and follow the rules there when writing or modifying the entity

Reviewing JPA Patterns

When the user asks to review JPA patterns, conventions, or code quality in the project:

  1. Detect current conventions by following references/entity-conventions.md (steps 1.1–1.5).
  2. Compare the detected conventions against the best practices defined in 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.

Working with Transactions

When the task involves adding or modifying transactional behavior:

  1. If transaction conventions have not been detected yet in this conversation — check memory for previously saved conventions first. If found in memory, reuse them. Otherwise read references/transaction-conventions.md and follow all substeps there to detect project conventions.
  2. Read references/transaction-rules-impl.md and follow the rules there when writing or modifying transactional code.