spring-data-jpa

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with good progressive-disclosure intent, but it delegates most executable detail to reference files (some of which are empty) and lacks validation checkpoints for destructive JPA/transaction changes.

Suggestions

Populate the empty transaction reference files (transaction-conventions.md, transaction-rules-impl.md) or remove their references, and fix the misspelled transaction-oregination.md filename.

Add an explicit validation/verification checkpoint to the entity and transaction workflows — e.g., verify mappings compile or run a schema/consistency check before declaring the change done.

Include a small concrete code or annotation example in the body for the most common task (e.g., a basic @Entity/@Repository skeleton) so the skill is actionable without opening the references.

Dimension	Reasoning	Score
Conciseness	The body is lean and action-oriented — numbered steps, a preflight checklist, and an output template — with no explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	It points to concrete reference files and gives a copy-ready review-output template, but the actual rule content lives in the references and the body itself gives no executable entity/transaction code, leaving key details incomplete.	2 / 3
Workflow Clarity	Steps are sequenced with a memory/preflight check, but for destructive database-mapping and transactional changes there are no validation or verification checkpoints, which the rubric caps at 2 for such operations.	2 / 3
Progressive Disclosure	References are one level deep and clearly signaled, but two referenced transaction files (transaction-conventions.md, transaction-rules-impl.md) are empty and a misspelled transaction-oregination.md is also empty, so the navigation is partly broken.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete on both what and when, and well-scoped to a distinct niche. It matches the strongest anchors across all dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'adding, removing, or modifying JPA entities, repositories, or projections' and 'changing entity structure, adding new entities, modifying field annotations, updating database mappings' — matching the top anchor for specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Rules and guidelines for working with Spring Data JPA') and when ('ALWAYS use this skill when...', 'Trigger on...'), satisfying the top anchor requiring explicit triggers for both.	3 / 3
Trigger Term Quality	Explicit 'Trigger on any request that involves...' followed by natural terms a user would say (entities, repositories, projections, field annotations, database mappings) giving broad coverage; not the level below which misses common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to Spring Data JPA entities/repositories/projections with distinct triggers, making it unlikely to fire for unrelated skills; clearly a clear niche.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Amplicode/spring-skills
Commit: 79e0e9c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.