springboot-tdd
使用JUnit 5、Mockito、MockMvc、Testcontainers和JaCoCo进行Spring Boot的测试驱动开发。适用于添加功能、修复错误或重构时。
84
77%
Does it follow best practices?
Impact
92%
1.26xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-CN/skills/springboot-tdd/SKILL.mdQuality
Discovery
75%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 description has a clear niche (Spring Boot TDD) with explicit 'when to use' guidance, making it complete and distinctive. However, it relies heavily on tool names rather than describing concrete actions, and could benefit from more natural language trigger terms that users might actually say when requesting testing help.
Suggestions
Add concrete actions like 'write unit tests', 'create integration tests', 'generate coverage reports', 'mock dependencies' to improve specificity
Include natural language trigger terms such as 'unit test', 'integration test', 'test coverage', 'mocking' alongside the tool names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spring Boot testing) and lists specific tools (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo), but doesn't describe concrete actions like 'write unit tests', 'generate test coverage reports', or 'create integration tests'. | 2 / 3 |
Completeness | Clearly answers both what (TDD with specific testing tools for Spring Boot) and when ('适用于添加功能、修复错误或重构时' = 'Use when adding features, fixing bugs, or refactoring'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes technical terms users might search for (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo, Spring Boot, TDD), but missing common natural language variations like 'unit test', 'integration test', 'test coverage', 'mocking', or English equivalents. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to Spring Boot testing with a distinct technology stack (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo). Unlikely to conflict with general coding skills or other language-specific testing skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
79%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, practical TDD skill for Spring Boot with excellent code examples covering unit, web, integration, and persistence testing. The content is concise and actionable, but could improve workflow clarity by adding explicit validation steps (e.g., what to do when coverage drops below 80%) and better progressive disclosure for advanced topics like Testcontainers configuration.
Suggestions
Add explicit validation checkpoints to the workflow section, e.g., 'Run `mvn verify` - if coverage < 80%, add tests before proceeding'
Include the TestContainersConfig class example or reference a separate file for Testcontainers setup details
Add a feedback loop for common failure scenarios (test failures, coverage gaps, flaky tests)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. No unnecessary explanations of what TDD is or how Spring Boot works - it assumes Claude's competence and jumps straight to actionable patterns. | 3 / 3 |
Actionability | Every section includes complete, executable code examples that are copy-paste ready. The Java test examples, Maven configuration, and CI commands are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The TDD workflow steps are listed (write test → implement → refactor → coverage) but lack explicit validation checkpoints. There's no feedback loop for when tests fail or coverage thresholds aren't met, which is important for TDD workflows. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's somewhat monolithic. The Testcontainers section mentions a TestContainersConfig class without showing it or referencing where to find it. Could benefit from linking to separate files for advanced topics like security testing or detailed JaCoCo configuration. | 2 / 3 |
Total | 10 / 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
- haniakrim21/everything-claude-code
- Commit
ae2cadd
- 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.