Claude Cursor Skill

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.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download codeaholicguy-ai-devkit-skills_dev-testing-ac73d58.zip · 1 KB

codeaholicguy/ai-devkit 1639 257 forks Apache-2.0 Updated 1d ago

Part of codeaholicguy/ai-devkit — 24 skills

Install

skills CLI npx skills add https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testing

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install codeaholicguy-ai-devkit@llmmart

Git git clone https://github.com/codeaholicguy/ai-devkit.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole codeaholicguy/ai-devkit collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

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

Files (ai-devkit)

agents

openai.yaml 209 B

interface:
  display_name: "Dev Testing"
  short_description: "AI DevKit · Write and verify feature test coverage"
  default_prompt: "Use $dev-testing to add tests, run coverage, and update the testing doc."

SKILL.md 1.9 KB

---
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

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. Apply the `verify` skill 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`.