springboot-tdd

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

1.21x

Quality

78%

Does it follow best practices?

Impact

100%

1.21x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/skills/springboot-tdd/SKILL.md

Quality

Content

82%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 dense, well-structured TDD reference with executable examples for every Spring Boot test layer and exact build/CI commands. The main gaps are the implicit (rather than explicit) validation checkpoints in the workflow and time-sensitive version pinning in the JaCoCo snippet.

Suggestions

Make the workflow's validation checkpoints explicit (e.g., 'run the new test and confirm it fails before implementing; re-run after refactoring') with a fix-and-retry loop.

Move the JaCoCo version-pinned Maven plugin configuration into a references file (or an old-patterns section) so the main body stays version-stable and leaner.

Add brief guidance on what to do when the coverage gate fails in CI (e.g., the mvn verify failure output and how to close the gap).

Dimension	Reasoning	Score
Conciseness	The body is lean — no explanations of what Spring Boot or JUnit is, just patterns and code ('パターン: Arrange-Act-Assert', '可読性のためにAssertJ（assertThat）を優先'). It is not a 5 because of time-sensitive detail: the JaCoCo snippet pins '<version>0.8.14</version>' and inlines a full Maven plugin configuration Claude could generate, with no old-patterns framing.	4 / 5
Actionability	Every section gives copy-paste-ready code or commands: complete @ExtendWith/@WebMvcTest/@SpringBootTest/@DataJpaTest test classes, a JaCoCo plugin snippet, and exact CI commands ('mvn -T 4 test', './gradlew test jacocoTestReport'). Coverage spans the common Spring testing layers (unit, web, integration, persistence, coverage).	5 / 5
Workflow Clarity	The TDD sequence is clearly listed ('1) テストを最初に書く（失敗すべき）... 4) カバレッジを強制（JaCoCo）') and the red-green-refactor loop is inherent, with '失敗すべき' acting as an implicit checkpoint. Not a 5 because validation checkpoints (confirm the test fails, re-run after refactor) are implied rather than explicit, and there is no error-recovery guidance; not a 3 because the sequence itself is coherent and complete.	4 / 5
Progressive Disclosure	Sections are well-organized and appropriately scoped for a single-file skill, and no bundle files exist to reference. It stops short of a 5: at ~150 lines it exceeds the simple-skill threshold, and reference-worthy material (the JaCoCo Maven config, per-layer test recipes) is inlined where a leaner SKILL.md pointing to references could sit.	4 / 5
	Total	17 / 20 Passed

Description

75%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.

A concise, specific description that clearly states what the skill does and when to use it, with a concrete technology stack. Its main weakness is that the trigger clause is generic code-work phrasing rather than testing- or Spring-specific terms users would naturally say.

Suggestions

Add testing-specific trigger phrases, e.g., 'Use when writing or running tests, improving test coverage, or adding integration tests for Spring Boot services'.

Include natural synonyms/extensions users say ('unit tests', 'MockMvc tests', 'test coverage') to strengthen trigger matching.

Dimension	Reasoning	Score
Specificity	The description names the domain and a comprehensive concrete toolset — 'Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo'. It lists specific technologies rather than multiple distinct actions, which keeps it just below the 5 anchor's 'multiple specific concrete actions' bar.	4 / 5
Completeness	Both parts are present: a clear 'what' (TDD for Spring Boot with the named toolset) and an explicit 'when' clause ('Use when adding features, fixing bugs, or refactoring'). Not a 5 because the when-clause is generic to any codebase rather than tied to concrete testing/Spring trigger phrases a user would utter.	4 / 5
Trigger Term Quality	'Use when adding features, fixing bugs, or refactoring' matches natural user phrasing. However, common testing terms users would actually say — 'write tests', 'unit test', 'test coverage', 'integration test' — are absent, so it falls at the 'good keyword coverage; a few natural terms missing' anchor rather than 5.	4 / 5
Distinctiveness Conflict Risk	The Spring Boot + JUnit 5/Mockito/MockMvc/Testcontainers/JaCoCo stack carves a clear niche with minimal conflict risk. Slight overlap remains with generic TDD or testing skills for other frameworks, and the broad when-clause ('adding features, fixing bugs, or refactoring') could match non-Spring work, placing it at 'mostly distinct; minor overlap risk'.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: docs/ja-JP/skills/springboot-tdd/SKILL.md
Commit: c70874f

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.