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; Write Mockito-first unit tests for Spring Boot services; Avoid unnecessary @SpringBootTest in Spring unit tests; Review Spring Boot slice-free unit test design. Part of Plinth Toolkit

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.

Well-structured overview with strong workflow validation and clean progressive disclosure to a real reference file. Weaker on conciseness (duplicated trigger list) and actionability (no inline executable code, abstract workflow verbs).

Suggestions

Remove or condense the 'When to use this skill' section, since its five bullets duplicate the trigger phrases already in the frontmatter description; keep a single source of truth for triggers.

Add one short inline good-vs-bad code example (e.g., @ExtendWith(MockitoExtension.class) service test vs. an unnecessary @SpringBootTest) in the body so guidance is executable without opening the reference.

Tighten workflow step 3 from 'Implement or refactor configuration/code following the reference patterns' to a concrete instruction naming the specific pattern to apply for the detected test type.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and avoids lecturing on concepts Claude already knows, but the 'When to use this skill' section repeats the same five trigger phrases already in the frontmatter description and the @322 redirect is duplicated, so it could be tightened.	2 / 3
Actionability	Concrete commands (./mvnw compile, mvn clean verify) and specific annotations are present, but the body defers all executable code/good-bad examples to the reference file and workflow step 3 ('Implement or refactor configuration/code following the reference patterns') is abstract rather than copy-paste ready.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced with explicit validation checkpoints and feedback loops: MANDATORY compile before changes, SAFETY stop-on-failure, and VERIFY clean verify afterward.	3 / 3
Progressive Disclosure	A concise overview body with a single, clearly signaled one-level-deep reference (references/321-frameworks-spring-boot-testing-unit-tests.md, which exists) holding the detailed rules and good/bad examples, with the reference linked both in the workflow and a dedicated Reference section.	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 highly specific, well-triggered description with clear scope boundaries and explicit cross-skill redirects. Its only weakness is the second-person 'you need' phrasing, which costs it one specificity point.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (pure unit tests with @ExtendWith(MockitoExtension.class), slice tests with @WebMvcTest/@MockitoBean, @JsonTest, parameterized @CsvSource/@MethodSource, @TestConfiguration), which would merit a 3, but the opening 'Use when you need to write unit tests' uses second-person voice ('you need'), triggering the one-point specificity penalty per the judging guidelines.	2 / 3
Completeness	Explicitly answers both what (the enumerated test types and annotations) and when ('Use when you need to write unit tests for Spring Boot applications' plus the 'This should trigger for requests such as' clause), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Strong coverage of natural phrases users would say, including 'Review Java code for Spring Boot unit tests', 'Apply best practices for Spring Boot unit tests', 'Write Mockito-first unit tests for Spring Boot services', and 'Avoid unnecessary @SpringBootTest'.	3 / 3
Distinctiveness Conflict Risk	Clear niche (Spring Boot unit testing) with distinct triggers, and it explicitly redirects framework-agnostic Java to @131-java-testing-unit-testing and integration tests to @322, preventing cross-skill conflicts.	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/plinth
Commit: aaee915

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.