springboot-tdd
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
86
66%
Does it follow best practices?
Impact
100%
1.21xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/ja-JP/skills/springboot-tdd/SKILL.mdQuality
Discovery
67%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 establishes a clear technology stack for Spring Boot testing but falls short on specifying concrete actions (what it actually does beyond 'TDD') and has overly broad trigger conditions that would cause conflicts with general development skills. The tool enumeration is helpful for disambiguation but the 'when' clause needs to be more specific to testing scenarios.
Suggestions
Add concrete actions like 'Writes unit and integration tests, configures mocks, sets up test containers for database testing, and generates coverage reports' to improve specificity.
Narrow the 'Use when...' clause to testing-specific triggers, e.g., 'Use when the user asks to write tests, improve test coverage, set up testing infrastructure, or needs help with JUnit/Mockito/MockMvc patterns in Spring Boot projects.'
| 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 mock configurations', 'set up integration tests with containers', or 'measure code coverage'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (test-driven development for Spring Boot with specific tools) and 'when' ('Use when adding features, fixing bugs, or refactoring'), though the 'when' clause is quite broad and could benefit from more specific triggers. | 3 / 3 |
Trigger Term Quality | Includes good technical keywords (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo, Spring Boot, TDD) that users familiar with the stack would use, but the trigger terms 'adding features, fixing bugs, or refactoring' are overly generic and would match nearly any development skill. Missing natural terms like 'unit test', 'integration test', 'test coverage', 'write tests'. | 2 / 3 |
Distinctiveness Conflict Risk | The Spring Boot + testing tools combination creates a reasonably distinct niche, but the 'Use when adding features, fixing bugs, or refactoring' trigger is extremely broad and would conflict with virtually any development-related skill. A general coding skill or Spring Boot development skill could easily be triggered by the same requests. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, actionable Spring Boot TDD skill with excellent executable code examples covering all major test layers. Its main weaknesses are the lack of explicit validation checkpoints in the TDD workflow (e.g., verifying test failure before implementation, checking coverage thresholds) and some unnecessary advice that Claude already knows. The content is well-structured but could benefit from tighter workflow sequencing with feedback loops.
Suggestions
Add explicit validation checkpoints to the workflow: e.g., 'Run `mvn test` — confirm the new test FAILS before writing implementation' and 'Run `mvn verify` — confirm coverage ≥ 80% in JaCoCo report at target/site/jacoco/index.html'
Remove guidance Claude already knows: 'Arrange-Act-Assert', 'avoid partial mocks', and the final reminder about tests being fast/isolated/deterministic — these consume tokens without adding value
Add a feedback loop for coverage failures: 'If coverage < 80%: identify untested branches with `mvn jacoco:report`, add targeted tests, re-run verify'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but includes some unnecessary guidance Claude already knows (e.g., 'Arrange-Act-Assert', 'avoid partial mocks', 'tests should be fast, isolated, deterministic'). The final reminder and some pattern notes are things Claude inherently understands. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for every test layer (unit, web, integration, persistence), plus concrete JaCoCo Maven configuration and CI commands. The test data builder pattern is also concrete and usable. | 3 / 3 |
Workflow Clarity | The TDD workflow (Red-Green-Refactor) is listed but lacks explicit validation checkpoints — there's no 'run tests and verify failure' step, no 'check coverage report and verify threshold' step, and no feedback loop for when coverage falls below 80%. For a workflow involving iterative test-code cycles, the absence of verification steps is notable. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers covering different test types, but it's somewhat monolithic — the JaCoCo config, Testcontainers setup details, and test data builder patterns could be split into referenced files. However, with no bundle files provided and the content being under ~120 lines, the inline approach is borderline acceptable. | 2 / 3 |
Total | 9 / 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
- affaan-m/everything-claude-code
- Commit
841beea
- 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.