132-java-testing-integration-testing

Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs. This should trigger for requests such as Review Java code for integration tests; Apply best practices for 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

85%

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

A concise, well-structured skill body with a clear validation-gated workflow and a clean one-level reference. Its only gap is actionability: all executable code lives in the reference rather than inline in the SKILL.md.

Suggestions

Include one short inline code snippet (e.g., a minimal BaseIntegrationTest or WireMock stub setup) so the body demonstrates the pattern without forcing a reference load.

Add a brief concrete example of the import-signal topology detection step in the workflow so step 2 is actionable on its own.

Dimension	Reasoning	Score
Conciseness	Lean, terse bullets describe capabilities without explaining what WireMock or integration tests are, assuming Claude's competence and earning every token.	3 / 3
Actionability	Concrete Maven commands ('./mvnw compile', 'mvn clean verify') are copy-paste ready, but the body defers all code to the reference and contains no inline executable examples, leaving some guidance incomplete rather than fully actionable.	2 / 3
Workflow Clarity	A clearly numbered workflow with explicit validation checkpoints — compile before changes, stop immediately if compilation fails, verify after — provides an explicit feedback loop for error recovery.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single well-signaled one-level-deep reference (references/132-java-testing-integration-testing.md, a real file), with content appropriately split for easy navigation.	3 / 3
	Total	11 / 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.

A highly specific, well-triggered description that names concrete capabilities and explicit 'Use when'/'should trigger for' guidance with a clear niche. No first/second-person voice issues; it reads in third person.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions such as 'generating a BaseIntegrationTest.java with WireMock', 'injecting service coordinates dynamically via System.setProperty()', and 'creating WireMock JSON mapping files with bodyFileName', matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (the enumerated capabilities) and when via 'Use when you need to set up, review, or improve...' and 'This should trigger for requests such as...', satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Includes natural trigger phrasing users would say — 'Review Java code for integration tests' and 'Apply best practices for integration tests in Java code' — giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The Java integration-testing-with-WireMock niche plus its specific trigger phrases make it clearly distinguishable and unlikely to fire for unrelated skills.	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: 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.