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 the skill actually does beyond 'TDD') and uses overly broad trigger conditions that would cause it to activate for nearly any development task. The tool enumeration is helpful for distinctiveness but the 'when' clause undermines it by being too generic.
Suggestions
Add specific concrete actions like 'Writes unit and integration tests, configures mocks, sets up test containers for database testing, and generates coverage reports'.
Narrow the 'Use when...' clause to testing-specific triggers: 'Use when writing tests, improving test coverage, setting up test infrastructure, or when the user mentions JUnit, Mockito, or test-driven development'.
Include natural user terms like 'unit test', 'integration test', 'test coverage', 'mock', 'test class' to improve trigger term coverage.
| 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 | Answers both 'what' (test-driven development for Spring Boot with specific tools) and 'when' (Use when adding features, fixing bugs, or refactoring) with an explicit 'Use when...' clause, though the 'when' triggers are quite broad. | 3 / 3 |
Trigger Term Quality | Includes good technical keywords (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo, Spring Boot) that users familiar with the stack would use, but the trigger terms 'adding features, fixing bugs, or refactoring' are overly generic and would match many non-testing skills. Missing natural terms like 'unit test', 'integration test', 'test coverage', 'write tests'. | 2 / 3 |
Distinctiveness Conflict Risk | The Spring Boot + testing tool stack creates a reasonably distinct niche, but the 'Use when adding features, fixing bugs, or refactoring' triggers are extremely broad and would conflict with virtually any development-related skill. A general Spring Boot development skill or a refactoring skill would easily overlap. | 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.
This is a solid, actionable Spring Boot TDD skill with excellent executable code examples covering all major test layers. Its main weaknesses are a somewhat verbose structure that could benefit from splitting advanced topics into referenced files, and a TDD workflow section that lacks explicit validation checkpoints and feedback loops (e.g., what to do when coverage is below threshold). Some general testing advice that Claude already knows could be trimmed.
Suggestions
Add explicit validation checkpoints to the workflow: e.g., 'Run `mvn test` → verify RED → implement → run again → verify GREEN → run `mvn verify` → check JaCoCo report at target/site/jacoco/index.html → if below 80%, add tests'
Move JaCoCo Maven/Gradle config and TestContainersConfig setup into separate referenced files (e.g., JACOCO_SETUP.md, TESTCONTAINERS_SETUP.md) to keep the main skill focused on the TDD workflow
Remove general testing advice Claude already knows (Arrange-Act-Assert pattern, 'test behavior not implementation', 'tests should be fast and isolated') to improve conciseness
| 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 'When to use' section is also somewhat redundant given the skill description. Could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for every test layer: unit tests with Mockito, MockMvc web layer tests, integration tests, DataJpaTest, JaCoCo Maven config, and test data builders. CI commands are concrete and specific. | 3 / 3 |
Workflow Clarity | The TDD workflow (Red-Green-Refactor) is listed but lacks explicit validation checkpoints. There's no feedback loop for when tests fail or coverage thresholds aren't met. For a TDD workflow, there should be explicit steps like 'run tests, verify failure, implement, run tests again, check coverage report, fix if below threshold.' | 2 / 3 |
Progressive Disclosure | Content is reasonably well-structured with clear section headers for each test type, but it's a fairly long monolithic file. The Testcontainers section mentions a TestContainersConfig class but doesn't link to a reference for it. JaCoCo configuration and test data builders could be split into separate reference files to keep the main skill leaner. | 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
5df943e
- 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.