Agent Skills › codeaholicguy/ai-devkit › dev-testing

dev-testing

GitHub

指导AI开发工具包测试阶段工作，包括编写单元测试和集成测试、分析覆盖率缺口及更新文档。执行前需运行lint并制定计划获批准，强调在声明通过前应用验证技能，并记录任务证据以闭环测试流程。

skills/dev-testing/SKILL.md codeaholicguy/ai-devkit

Trigger Scenarios

用户希望编写或更新功能测试用例需要运行代码覆盖率分析用户明确要求关闭测试覆盖缺口触发开发生命周期第8阶段

Install

npx skills add codeaholicguy/ai-devkit --skill dev-testing -g -y

More Options

Use without installing

npx skills use codeaholicguy/ai-devkit@dev-testing

指定 Agent (Claude Code)

npx skills add codeaholicguy/ai-devkit --skill dev-testing -a claude-code -g -y

安装 repo 全部 skill

npx skills add codeaholicguy/ai-devkit --all -g -y

预览 repo 内 skill

npx skills add codeaholicguy/ai-devkit --list

SKILL.md

Frontmatter

{
    "name": "dev-testing",
    "description": "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."
}

Dev Testing

Run testing work for configured AI docs features. Before changing docs or code, propose the concrete plan for this phase and wait for user approval unless the user already approved the exact phase plan.

Phase Contract

Run npx ai-devkit@latest lint before phase work.
If working on a named feature, run npx ai-devkit@latest lint --feature <name>.
Read the testing doc, requirements, design, implementation notes, and current diff before changes.
Apply the verify skill before making coverage or test-pass claims.
If parent dev-lifecycle established usable task tracing, emit testing phase, next-action, and evidence events per task.

Write Tests

Use for Phase 8.

Run npx ai-devkit@latest lint --feature <name> and reference the testing doc path it validates. If manual path resolution is unavoidable, first resolve .ai-devkit.json paths.docs, falling back to docs/ai.
Gather context: feature name, changes summary, environment, existing test suites, flaky tests to avoid.
Analyze the testing template, success criteria, edge cases, available mocks, and fixtures.
Add unit tests for happy paths, edge cases, and error handling for each module. Highlight missing branches.
Add integration tests for critical cross-component flows, setup/teardown, and boundary/failure cases.
Run coverage tooling, identify gaps, and suggest additional tests if below the target.
If task tracing is available, record evidence for each fresh test/coverage command per task.
Update the selected testing doc with test file links and results.