322-frameworks-spring-boot-testing-integration-tests

Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

A well-structured overview with strong workflow gating and clean progressive disclosure, but it duplicates frontmatter content and delegates all executable test code to the reference, weakening conciseness and actionability.

Suggestions

Remove or compress the 'What is covered in this Skill?' and 'When to use this skill' sections, since they restate the frontmatter description and waste tokens already in context.

Add one short executable code snippet in the body (e.g. a @ServiceConnection + static @Container test skeleton) so core guidance is actionable without opening the reference.

Tighten step 3 from 'Implement or refactor configuration/code following the reference patterns' to name the specific patterns to apply, reducing reliance on the deferred reference.

Dimension	Reasoning	Score
Conciseness	The 'What is covered in this Skill?' bullet list and the 'When to use this skill' section largely restate the frontmatter description, duplicating content Claude already received; the body is otherwise lean and free of basic-concept padding.	2 / 3
Actionability	Concrete commands are present ('./mvnw compile', 'mvn clean verify'), but all actual test code and good/bad examples are deferred to the reference and step 3 only says to 'Implement or refactor configuration/code following the reference patterns', which is abstract rather than copy-paste ready.	2 / 3
Workflow Clarity	Four sequenced steps with explicit validation checkpoints: MANDATORY compile-before, SAFETY stop-on-failure, VERIFY clean-verify-after, plus edge-case handling (ask a clarifying question if scope is ambiguous, report missing inputs), satisfying the feedback-loop requirement.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep reference file (references/322-frameworks-spring-boot-testing-integration-tests.md, confirmed to exist), clearly signaled in both the Workflow and Reference sections.	3 / 3
	Total	10 / 12 Passed

Description

90%

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

A strong, specific description with explicit trigger phrases and a clear niche. Its only weakness is the second-person 'Use when you need to' voice, which the rubric penalizes on specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Testcontainers with @ServiceConnection', '@DataJdbcTest persistence slices', 'TestRestTemplate or MockMvcTester for HTTP', 'data isolation, and container lifecycle management'), which would be a 3, but the opening 'Use when you need to...' uses second-person voice, triggering the rubric's -1 specificity penalty.	2 / 3
Completeness	Clearly answers both what (write/improve integration tests with the listed techniques) and when ('Use when you need to...' plus 'This should trigger for requests such as...'), with explicit triggers rather than implied ones.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases users would say are quoted verbatim: 'Review Java code for Spring Boot integration tests' and 'Apply best practices for Spring Boot integration tests in Java code', alongside concrete terms like Testcontainers and Spring Boot 4.0.x.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Spring Boot integration tests with distinct triggers, making it unlikely to fire for a sibling unit-testing skill; the trailing 'Part of cursor-rules-java project' is informational and does not blur the niche.	3 / 3
	Total	11 / 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: jabrena/cursor-rules-java
Commit: 86eb63d

Reviewed: 1 day 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.