321-frameworks-spring-boot-testing-unit-tests

Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. This should trigger for requests such as Review Java code for Spring Boot unit tests; Apply best practices for Spring Boot unit 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

85%

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

A well-structured, concise skill body with an explicit validation-gated workflow and clean one-level-deep reference. The main gap is that executable test examples live only in the reference file rather than the body.

Suggestions

Include one minimal copy-paste-ready example (e.g. a pure @ExtendWith(MockitoExtension.class) test stub and a @WebMvcTest slice) directly in the body so the core pattern is actionable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean: a tight 'What is covered' bullet list and brief workflow with no re-explanation of Mockito/Spring concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Concrete commands are present ('./mvnw compile', 'mvn clean verify') and specific annotations are named, but no executable test code lives in the body — the actual good/bad examples are deferred to the reference file, leaving the core testing guidance non-copy-paste-ready here.	2 / 3
Workflow Clarity	A clear 4-step workflow with explicit validation checkpoints (MANDATORY compile-before, SAFETY stop-on-failure, VERIFY after) and a feedback loop for error recovery.	3 / 3
Progressive Disclosure	The body is an overview that signals a single one-level-deep reference (references/321-frameworks-spring-boot-testing-unit-tests.md, verified to exist) in multiple places; content is appropriately split with easy navigation.	3 / 3
	Total	11 / 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 triggers and clear disambiguation from sibling skills. The only issue is second-person voice in the trigger clause, which the rubric penalizes.

Suggestions

Reword the trigger clause to third person, e.g. 'Use when writing unit tests for Spring Boot applications' instead of 'Use when you need to write', to satisfy the rubric's voice requirement and recover the specificity point.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (pure unit tests with @ExtendWith(MockitoExtension.class), slice tests with @WebMvcTest, @JsonTest, parameterized tests with @CsvSource/@MethodSource, @TestConfiguration), which would warrant 3, but the second-person phrasing 'Use when you need to write' triggers the rubric's one-point voice penalty.	2 / 3
Completeness	Explicitly answers both what (detailed enumeration of test types and annotations) and when (an explicit 'Use when...' clause plus concrete trigger-example sentences).	3 / 3
Trigger Term Quality	Includes natural trigger phrases users would say — 'Review Java code for Spring Boot unit tests' and 'Apply best practices for Spring Boot unit tests in Java code' — plus strong keyword coverage of the domain.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly scoped to Spring Boot unit testing and disambiguated from sibling skills via explicit pointers to @131-java-testing-unit-testing and @322...integration-tests.	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: 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.