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
74
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/322-frameworks-spring-boot-testing-integration-tests/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly defines its scope around Spring Boot 4.0.x integration testing with specific technologies and patterns. It opens with an explicit 'Use when' clause, lists concrete capabilities, and provides example trigger phrases. The only minor weakness is slight verbosity, but the detail serves the purpose of disambiguation well.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management. These are highly specific capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (write/improve integration tests with specific technologies) and 'when' (explicit 'Use when' clause at the start, plus 'This should trigger for requests such as...' with concrete examples). Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'integration tests', 'Testcontainers', 'Spring Boot', '@DataJdbcTest', 'TestRestTemplate', 'MockMvcTester', 'best practices', 'Java code'. Also includes explicit trigger phrases like 'Review Java code for Spring Boot integration tests'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Spring Boot 4.0.x integration testing with specific annotations and tools. The combination of version-specific Spring Boot, Testcontainers, @ServiceConnection, @DataJdbcTest, and MockMvcTester creates a very clear and unique scope unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a pointer to an external reference file, with almost no actionable content in the body itself. While the workflow structure and constraints are reasonable, the lack of any concrete code examples, specific patterns, or executable guidance means Claude would need to read the entire reference file before being able to act. The bullet list of covered topics adds tokens without adding actionable value.
Suggestions
Add at least 2-3 concrete, copy-paste-ready code examples inline (e.g., a Testcontainers @ServiceConnection setup, a MockMvcTester assertion, a @DataJdbcTest slice) so the skill is actionable without reading the reference file.
Replace the abstract workflow step 'Apply framework-aligned changes' with specific sub-steps showing what patterns to look for and what to change (e.g., 'Replace @MockBean with @MockitoBean', 'Convert RestAssured calls to MockMvcTester').
Add a good/bad pattern comparison directly in the skill body for the most common transformation (e.g., before/after for Testcontainers setup) to make the skill immediately useful.
Trim the 'What is covered' bullet list—it reads like a syllabus and consumes tokens without teaching anything Claude can act on.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is essentially a table of contents for content that lives in the reference file, adding moderate bloat. The constraints and workflow sections are reasonably tight but could be tighter—e.g., the bullet list repeats information Claude already knows about Spring Boot testing concepts. | 2 / 3 |
Actionability | There are no concrete code examples, executable commands beyond generic mvnw invocations, or copy-paste-ready patterns. All substantive guidance is deferred to the reference file. The skill body describes what to do abstractly ('Apply framework-aligned changes') rather than showing how. | 1 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced and includes a compilation check and verification step, which is good. However, the steps are vague ('Apply framework-aligned changes') with no validation checkpoints between sub-steps, and the feedback loop for failure is limited to 'stop immediately' without recovery guidance. | 2 / 3 |
Progressive Disclosure | The skill correctly references a single external file for detailed rules and patterns, which is good one-level-deep disclosure. However, the bundle files were not provided, so we cannot verify the reference exists, and the skill body itself contains too little actionable content—it over-delegates to the reference without providing a useful quick-start summary. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
762cb86
- Reviewed
Table of Contents
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.