golang-testing

保证测试驱动开发与 Go 代码高质量的全面测试策略。

Quality

61%

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/golang-testing/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with abundant executable Go and CLI examples, but it is verbose for a skill body and monolithic — explaining well-known concepts inline with no progressive disclosure to reference files. It also lacks validation feedback loops for risky operations like database and integration testing.

Suggestions

Trim the body to a concise overview of core patterns and move advanced material (deep mocking, testcontainers, fuzzing, benchmarking comparisons) into reference files linked from the top of the document.

Remove or compress explanations of basic concepts Claude already knows (t.Helper, t.Parallel, simple if-got-want assertions) and keep only Go-specific guidance.

Add explicit validation/verification checkpoints to the database and integration-test workflows (e.g. verify connection/migration succeeded before proceeding, re-run on failure) to support destructive/batch operations.

Dimension	Reasoning	Score
Conciseness	The ~960-line body is a thorough inline reference manual that explains concepts Claude already knows (t.Helper, t.Parallel, table-driven tests, httptest) at length, and is not trimmed to a lean overview.	2 / 3
Actionability	Provides extensive executable Go code and concrete shell commands (go test -coverprofile, -race, -fuzz, httptest.NewRequest) that are specific and copy-paste ready.	3 / 3
Workflow Clarity	Sections are organized and the TDD loop is sequenced, but there are no explicit validation checkpoints or error-recovery loops for destructive/batch operations like DB transaction tests and testcontainers setup.	2 / 3
Progressive Disclosure	A monolithic single file with no bundle references; advanced topics (mocking, testcontainers, fuzzing) that should be split out are inlined rather than linked from a concise overview.	2 / 3
	Total	9 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 conveys a clear Go-testing niche but is vague on concrete actions and, critically, omits any explicit activation triggers. It reads as a formal capability statement rather than a trigger-rich, natural-language description.

Suggestions

Replace the abstract "全面测试策略" with concrete actions: e.g. writing table-driven tests, mocking interfaces, benchmarks, fuzzing, and coverage analysis.

Add an explicit trigger clause such as "Use when writing, reviewing, or improving Go tests, or when the user mentions Go testing, TDD, test coverage, benchmarks, or fuzzing."

Include natural user-facing terms (单元测试, 测试覆盖率, 基准测试, 表格驱动测试) alongside TDD and Go to improve trigger recall.

Dimension	Reasoning	Score
Specificity	Names the Go-testing domain and a broad purpose ("保证测试驱动开发与 Go 代码高质量的全面测试策略") but uses the vague phrase "全面测试策略" instead of listing concrete actions such as writing tests, mocking, benchmarks, or fuzzing.	2 / 3
Completeness	States clearly what the skill does but provides no "Use when..." / 使用场景 trigger guidance, so the "when" is entirely missing rather than explicit.	2 / 3
Trigger Term Quality	Includes real relevant terms ("测试驱动开发", "Go 代码", "测试") but the phrasing is formal rather than natural user speech and omits common variations like 单元测试, 测试覆盖率, and 基准测试.	2 / 3
Distinctiveness Conflict Risk	The combination of Go and testing/TDD carves out a clear, specific niche that is unlikely to overlap with non-Go or non-testing skills.	3 / 3
	Total	9 / 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
skill_md_line_count	SKILL.md is long (960 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/golang-testing/SKILL.md
Commit: dfbf946

Reviewed: 29 days 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.