springboot-tdd

使用JUnit 5、Mockito、MockMvc、Testcontainers和JaCoCo进行Spring Boot的测试驱动开发。适用于添加功能、修复错误或重构时。

1.31x

Quality

70%

Does it follow best practices?

Impact

96%

1.31x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-CN/skills/springboot-tdd/SKILL.md

Quality

Content

64%Scale 1-3

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

This is a solid, actionable Spring Boot TDD skill with excellent concrete code examples across all testing layers. Its main weaknesses are the lack of explicit validation checkpoints in the workflow (e.g., verifying test failure before implementation, checking coverage thresholds) and some unnecessary explanatory content that Claude already knows. The monolithic structure is acceptable for the content volume but could benefit from external references for advanced topics.

Suggestions

Add explicit validation checkpoints to the workflow: e.g., 'Run `mvn test` — confirm new test FAILS before writing implementation' and 'Run `mvn verify` — confirm coverage ≥ 80% before committing'

Remove guidance Claude already knows: 'Arrange-Act-Assert' pattern name, 'test behavior not implementation details', and the 'When to use' section which restates the frontmatter description

Add a JaCoCo coverage enforcement rule (e.g., `<rule><limit><minimum>0.80</minimum></limit></rule>`) since the skill promises 80%+ coverage but doesn't show how to enforce it

Dimension	Reasoning	Score
Conciseness	Generally efficient with good code examples, but includes some unnecessary guidance Claude already knows (e.g., 'Arrange-Act-Assert', 'test behavior not implementation details', explaining when to use TDD). The assertions section and some pattern notes could be trimmed.	2 / 3
Actionability	Provides fully executable, copy-paste ready code examples for every testing layer (unit, web, integration, persistence), complete with annotations, imports context, and concrete Maven/Gradle commands. The JaCoCo XML config is directly usable.	3 / 3
Workflow Clarity	The 4-step TDD workflow is listed but lacks explicit validation checkpoints — there's no 'run tests and verify they fail' step with a concrete command, no feedback loop for when coverage thresholds aren't met, and no explicit verification between steps. For a workflow involving iterative test-code cycles, the sequencing is too implicit.	2 / 3
Progressive Disclosure	Content is reasonably well-structured with clear section headers, but it's a monolithic file with no references to external files. The Testcontainers section is notably thin and could benefit from a separate detailed reference. The JaCoCo coverage threshold configuration is missing and could be split out. For a skill of this length (~120 lines), some content could be externalized.	2 / 3
	Total	9 / 12 Passed

Description

75%Scale 1-3

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

The description effectively identifies its niche (Spring Boot TDD) and provides explicit trigger conditions for when to use it. Its main weakness is that it lists tools rather than describing concrete actions performed with those tools, and it could benefit from more natural language trigger terms. The explicit 'when' clause is a strong point that many descriptions lack.

Suggestions

Add concrete actions like 'writes unit and integration tests, mocks dependencies, configures test containers, measures code coverage' instead of relying on tool names alone to convey capabilities.

Include natural language trigger terms such as 'unit test', 'integration test', 'test coverage', 'write tests', 'mock service' to improve matching when users describe their needs in plain language rather than tool names.

Dimension	Reasoning	Score
Specificity	Names the domain (Spring Boot TDD) and lists specific tools (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo), but does not describe concrete actions like 'write unit tests', 'generate test classes', 'mock dependencies', or 'measure code coverage'. The tools are named but what is actually done with them is left vague under the umbrella term 'test-driven development'.	2 / 3
Completeness	Clearly answers both 'what' (TDD for Spring Boot using specific testing frameworks) and 'when' (when adding features, fixing bugs, or refactoring). The '适用于添加功能、修复错误或重构时' clause serves as an explicit 'Use when...' trigger.	3 / 3
Trigger Term Quality	Includes relevant technical keywords (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo, Spring Boot, TDD) that a developer might mention, but misses common natural language variations like 'unit test', 'integration test', 'test coverage', 'write tests', 'testing', or English equivalents that users might use in mixed-language environments.	2 / 3
Distinctiveness Conflict Risk	The combination of Spring Boot + TDD + specific testing tools (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo) creates a very clear niche that is unlikely to conflict with other skills. It is distinctly about Java/Spring Boot testing, not general testing or other frameworks.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: affaan-m/ECC
Path: docs/zh-CN/skills/springboot-tdd/SKILL.md
Commit: 06c5e11

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.