tdd-workflow

在编写新功能、修复错误或重构代码时使用此技能。强制执行测试驱动开发，确保单元测试、集成测试和端到端测试的覆盖率超过80%。

Quality

70%

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/zh-CN/skills/tdd-workflow/SKILL.md

Quality

Content

71%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 highly actionable TDD reference with executable code and a well-sequenced workflow, but it is over-long for a SKILL.md, over-explains basics Claude already knows, and does not split its bulk into reference files.

Suggestions

Move the long mock patterns, test-type catalog, and best-practices list into separate reference files (e.g. references/mock-patterns.md) and link them from a concise SKILL.md overview to improve progressive_disclosure and conciseness.

Trim sections that restate common knowledge (e.g. definitions of unit/integration/e2e tests, the closing 'remember tests are not optional' line) to assume Claude's competence.

Add an explicit feedback loop after step 5 and step 7 (e.g. 'if coverage is below 80%, add tests for uncovered branches and re-run') to strengthen workflow_clarity.

Dimension	Reasoning	Score
Conciseness	The ~430-line body is mostly efficient with concrete examples, but sections like '测试类型' explain concepts Claude already knows and the closing '记住：测试不是可选的' is padding, fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	Provides copy-paste-ready executable TypeScript (Jest/Vitest, Playwright), bash commands (npm test, npm run test:coverage), mock patterns, and a coverage-threshold JSON config covering the common cases comprehensively.	5 / 5
Workflow Clarity	The 7-step TDD sequence is clearly ordered with checkpoints (tests should fail in step 3, pass in step 5, coverage verified in step 7), but lacks explicit error-recovery feedback loops, fitting 'clear sequence with most checkpoints, minor gaps'.	4 / 5
Progressive Disclosure	Well-organized with clear section headers, but at ~430 lines everything (mock patterns, test patterns, best-practices list) is inlined into a single monolithic file with no file splitting or external references; the under-50-line simple-skill exception does not apply.	3 / 5
	Total	15 / 20 Passed

Description

70%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 clear, third-person description that states both what the skill does and when to use it with concrete trigger phrases. It is slightly held back by a high-level rather than comprehensive enumeration of capabilities.

Dimension	Reasoning	Score
Specificity	Names the TDD domain with two concrete actions ('强制执行测试驱动开发', '确保...覆盖率超过80%') but does not enumerate a comprehensive list of specific behaviors, fitting the 'domain + 1-2 actions' anchor rather than the multi-action anchor at 4.	3 / 5
Completeness	Both 'what' (enforces TDD, ensures >80% coverage) and 'when' (writing features, fixing bugs, refactoring) are explicit and concrete, though the 'what' side stays high-level rather than fully enumerating capabilities.	4 / 5
Trigger Term Quality	Natural user-facing triggers are present ('编写新功能、修复错误或重构代码时') alongside '测试驱动开发', giving good keyword coverage with only minor synonym variants missing.	4 / 5
Distinctiveness Conflict Risk	The TDD + coverage-threshold niche is distinct from general coding skills, with only minor overlap risk against sibling testing skills; triggers are specific enough to avoid broad conflicts.	4 / 5
	Total	15 / 20 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: affaan-m/ECC
Path: docs/zh-CN/skills/tdd-workflow/SKILL.md
Commit: e04ea0b

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