springboot-tdd

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

1.31x

Quality

71%

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

76%Weight 40%Scale 1-5

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

A highly actionable, code-dense TDD reference with excellent executable examples across all Spring Boot test layers. The main weakness is workflow_clarity: the TDD loop lacks explicit validation gates and the coverage threshold is stated but not wired in as a checkpoint.

Suggestions

Add explicit validation checkpoints to the workflow, e.g. '1. Write failing test → run `mvn test`, confirm it fails for the right reason; 2. Implement minimum code → run tests, confirm pass; 3. Refactor → re-run tests; 4. Enforce coverage → `mvn verify` and confirm JaCoCo ≥ 80% before merging'.

Move or annotate the pinned JaCoCo version ('0.8.14') as a 'verify before use' detail so a stale version number does not silently age.

State the 80% coverage threshold as an explicit workflow gate rather than only in the header line so the failure path (coverage below target) is defined.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-driven with no padding or explanation of concepts Claude already knows, but the pinned JaCoCo version '0.8.14' is time-sensitive and not isolated in a deprecated section, a minor inefficiency.	4 / 5
Actionability	Fully executable, copy-paste-ready code spans unit, web, integration, and persistence layers plus concrete Maven/Gradle CI commands and a JaCoCo plugin snippet, covering the common Spring Boot TDD cases.	5 / 5
Workflow Clarity	The four-step workflow (failing test → minimal impl → refactor → enforce coverage) gives a clear sequence, but validation checkpoints are implicit—there is no explicit 'confirm tests fail first', 'run tests before refactor', or 'verify coverage ≥80% before proceeding' gate.	3 / 5
Progressive Disclosure	Content is well organized into clearly headed sections in a single file with no nested references, though at ~160 inlined lines it is slightly above the simple-skill threshold that would warrant a 5.	4 / 5
	Total	16 / 20 Passed

Description

67%Weight 40%Scale 1-5

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 is specific and tool-rich with an explicit use-when clause, but the trigger terms are broad and could include more natural synonyms. Voice is correctly third person with no over-claims.

Suggestions

Add concrete trigger synonyms users actually say (e.g. 'Spring Boot 单元测试', '集成测试', '覆盖率不足', 'testcontainers', 'jacoco 报告') to broaden natural keyword coverage.

Tighten the 'when' clause to name explicit triggers like 'Use when adding a new endpoint, fixing a failing Spring Boot test, or raising JaCoCo coverage above 80%'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Spring Boot的测试驱动开发') and several concrete tools (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo) but does not enumerate multiple distinct testing actions, so it sits at 'several specific actions with minor gaps' rather than comprehensive.	4 / 5
Completeness	It has a clear 'what' (TDD for Spring Boot with named tools) and an explicit 'when' ('适用于添加功能、修复错误或重构时'), but the 'when' could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger clause '适用于添加功能、修复错误或重构时' provides some natural terms users would say, but the phrases are broad and lack common synonyms or specific file/extension variations.	3 / 5
Distinctiveness Conflict Risk	The Spring Boot TDD niche with a specific tool stack is mostly distinct with only minor overlap risk against general testing skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

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

Reviewed: 2 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.