dev-testing

AI DevKit · Testing phase guidance for adding and validating feature test coverage. Use when the user wants to write tests, update testing docs, run coverage, close coverage gaps, or run dev-lifecycle phase 8.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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 tight, well-structured procedural skill: concrete commands, explicit validation gates, and a feedback loop back to dev-design. The only gaps are implicit tooling specifics in the coverage steps and no explicit test-pass confirmation checkpoint within the write-tests sequence.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: every step is an imperative instruction with no concept explanations or padding ('Run `npx ai-devkit@latest lint` before phase work', 'Gather context: feature name, changes summary, environment'), fully assuming Claude's competence.	5 / 5
Actionability	Provides executable commands (`npx ai-devkit@latest lint --feature <name>`) and a concrete path-resolution fallback via `.ai-devkit.json`, but steps like 'Run coverage tooling' and 'Analyze the testing template' leave tooling and doc specifics implicit.	4 / 5
Workflow Clarity	Clear sequenced steps with an upfront lint gate, an explicit validation rule ('Apply the `verify` skill before making coverage or test-pass claims'), and a feedback loop ('If tests reveal design flaws, return to `dev-design`'). Not 5 because the write-tests steps lack an explicit re-run-until-green checkpoint inside the loop.	4 / 5
Progressive Disclosure	A short (under 50 lines), single-purpose skill with no bundle files and no external references needed; content is appropriately split into well-organized 'Phase Contract' and 'Write Tests' sections with clear next-step navigation.	5 / 5
	Total	18 / 20 Passed

Description

83%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 strong description with an explicit 'Use when' clause covering five concrete triggers and a clearly stated capability set. Its main weaknesses are the mildly meta opening clause and a few missing natural synonyms for test-related requests.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('write tests, update testing docs, run coverage, close coverage gaps') but the lead clause 'Testing phase guidance for adding and validating feature test coverage' is slightly abstract, leaving minor gaps in coverage detail.	4 / 5
Completeness	Explicitly answers both what ('adding and validating feature test coverage') and when, via a clear 'Use when the user wants to write tests, update testing docs, run coverage, close coverage gaps, or run dev-lifecycle phase 8' clause with concrete triggers.	5 / 5
Trigger Term Quality	Good natural trigger phrases ('write tests', 'run coverage', 'coverage gaps') that users would actually say, though common synonyms like 'add tests', 'unit tests', or 'test suite' are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'AI DevKit' and 'dev-lifecycle phase 8' giving a distinct niche, but generic triggers like 'write tests' create minor overlap risk with general testing skills.	4 / 5
	Total	17 / 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: codeaholicguy/ai-devkit
Path: skills/dev-testing/SKILL.md
Commit: 7ef0cd5

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