Skill1.4k repo starsupdated yesterday

dev-testing

The dev-testing skill guides users through Phase 8 of an AI development lifecycle, helping them write unit and integration tests, measure code coverage, and validate test documentation for configured features. Use it when you need to add comprehensive test coverage, close coverage gaps, run coverage analysis, update testing documentation, or complete the testing phase of feature development.

View source Repository: ai-devkit

Install in Claude Code

Copy

git clone --depth 1 https://github.com/codeaholicguy/ai-devkit /tmp/dev-testing && cp -r /tmp/dev-testing/skills/dev-testing ~/.claude/skills/dev-testing

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

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

## 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. Update the selected testing doc with test file links and results.

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