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.
Profile →npx skills add codeaholicguy/ai-devkit --skill dev-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 mo
- Phase Contract
- Write Tests
What does the dev-testing skill do?
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.
How do I install it?
Run `npx skills add codeaholicguy/ai-devkit --skill dev-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From codeaholicguy/ai-devkit, a repository with 1,572 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.