Skip to main content

Workflow skill

Dev Testing Skill

Add and validate test coverage for feature work.

On this page

Install command

AI DevKit installs its built-in skills as one curated set. Run this once to install dev-testing with the rest of the built-in workflow skills.

bash
npx ai-devkit@latest skill add --built-in

What it does

Use dev-testing when implementation needs focused test coverage, coverage gap review, or validation before final review.

When to use it

  • Add targeted tests for a feature
  • Validate coverage gaps
  • Run evidence-backed test checks

Supported agents

  • Claude Code
  • Codex
  • Cursor
  • opencode

The SKILL.md file

This is what your agent reads when the skill runs. View it on GitHub (opens in a new tab)

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#

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

Write Tests#

Use for Phase 8.

  1. 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.
  2. Gather context: feature name, changes summary, environment, existing test suites, flaky tests to avoid.
  3. Analyze the testing template, success criteria, edge cases, available mocks, and fixtures.
  4. Add unit tests for happy paths, edge cases, and error handling for each module. Highlight missing branches.
  5. Add integration tests for critical cross-component flows, setup/teardown, and boundary/failure cases.
  6. Run coverage tooling, identify gaps, and suggest additional tests if below the target.
  7. If task tracing is available, record evidence for each fresh test/coverage command per task.
  8. Update the selected testing doc with test file links and results.

Next: dev-review. If tests reveal design flaws, return to dev-design.

esc