agentsclimarketplace

Dev testing

Skill codeaholicguy/ai-devkit/skills/dev-testing

The control plane for AI coding agents.

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.9 KB, as published. Nobody here has run it

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.