springboot-verification

Spring Boot 项目的验证循环：构建、静态分析、带有覆盖率的测试、安全扫描以及发布或 PR 前的差异审查。

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

A highly actionable, clearly sequenced verification pipeline with strong validation checkpoints and copy-paste commands. It is somewhat verbose (full test classes, bilingual glossing) and keeps all content inline without progressive disclosure via reference files.

Suggestions

Trim the three full Java test classes to one representative example or condensed snippets, moving detailed variants to a reference file, to improve token efficiency.

Reduce redundant bilingual parenthetical glossing on common terms (e.g. '构建 (Build)', '测试 (Test)') where the term is self-explanatory.

Introduce a references/ file (e.g. TEST_PATTERNS.md) for the extended unit/integration/API test examples and link to it from the Tests phase to practice one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and code, but three full Java test classes (~120 lines) plus pervasive bilingual parenthetical glossing on every term (e.g. '构建 (Build)', '测试 (Test)') add tokens that could be trimmed, matching the score-2 'mostly efficient but could be tightened' anchor rather than the score-3 'every token earns its place' anchor.	2 / 3
Actionability	It provides copy-paste-ready commands ('mvn -T 4 clean verify', 'spotbugs:check pmd:check checkstyle:check', targeted grep patterns) and complete executable Java test examples, matching the score-3 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Six phases are clearly sequenced with explicit validation checkpoints — '如果构建失败，请停止并修复', the 80% coverage threshold, a diff-review checklist, and a pass/fail report template — matching the score-3 'clear sequence with explicit validation steps and checklists' anchor.	3 / 3
Progressive Disclosure	The skill is a single ~230-line SKILL.md with no bundle/reference files and all content inline; it is well-sectioned but does not split the substantial test/security code into one-level-deep references, so it sits at the score-2 'some structure, content that could be separate is inline' anchor rather than the score-3 'well-signaled one-level-deep references' anchor.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-scoped description that names concrete verification actions and natural trigger terms with low conflict risk. Its main gap is the absence of an explicit 'Use when...' clause, leaving the usage timing only partially stated.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use before opening a PR, after major refactors/dependency upgrades, or prior to a release/deployment for a Spring Boot service.'

Make the timing guidance apply to the whole skill rather than only the diff-review phase, so the 'when' is unambiguous.

Include a couple of common phrasings users might say (e.g. 'run the verification pipeline', 'check coverage before merge') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — '构建、静态分析、带覆盖率的测试、安全扫描，以及...差异审查' (build, static analysis, tests with coverage, security scan, diff review) — matching the 'lists multiple specific concrete actions' anchor rather than the score-2 'some actions' anchor.	3 / 3
Completeness	The 'what' is explicit, but the 'when' is only partial ('发布或 PR 前的...差异审查' scopes the timing to one phase) and there is no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 2 rather than reaching the score-3 'clearly answers both what AND when with explicit triggers' anchor.	2 / 3
Trigger Term Quality	It uses natural terms a user would say when needing this skill — 'Spring Boot', '构建', '测试', '覆盖率', '安全扫描', 'PR', '发布' — giving good coverage of the domain's common vocabulary, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	'Spring Boot 项目验证循环' carves a clear niche with distinct triggers (Spring Boot, build/test/coverage/security/PR) unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 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: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/springboot-verification/SKILL.md
Commit: dfbf946

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