E2E Test Thinker
UniClipboard/UniClipboard
Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.
AI DevKit · Testing phase guidance for adding and validating feature test coverage.
Install Dev Testing
$ npx skills add codeaholicguy/ai-devkit --skill dev-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dev-testing .claude/skills/dev-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dev-testing" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testing into .claude/skills/dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add codeaholicguy/ai-devkit --skill dev-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/dev-testing .agents/skills/dev-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dev-testing" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testing into .agents/skills/dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codeaholicguy/ai-devkit --skill dev-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/dev-testing .cursor/skills/dev-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dev-testing" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testing into .cursor/skills/dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/codeaholicguy/ai-devkit.git --path skills/dev-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add codeaholicguy/ai-devkit --skill dev-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/dev-testing .gemini/skills/dev-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dev-testing" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testing into .gemini/skills/dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install codeaholicguy/ai-devkit dev-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add codeaholicguy/ai-devkit --skill dev-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/dev-testing .github/skills/dev-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dev-testing" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testing into .github/skills/dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codeaholicguy/ai-devkit --skill dev-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install codeaholicguy/ai-devkit dev-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/dev-testing .opencode/skills/dev-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dev-testing" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/dev-testing into .opencode/skills/dev-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dev-testing- GitHub stars
- 1.6k
- Token cost
- ~482 tokens
- SKILL.md length
- 245 words
- Files
- 2
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
AI DevKit · Testing phase guidance for adding and validating feature test coverage.
- Works in 5 steps: Run npx ai-devkit@latest lint before… → If working on a named feature, run npx… → Read the testing doc, requirements,… → …
- The user wants to write tests
- SKILL.md covers Phase Contract and Write Tests
- Calls npx
What it does
Dev Testing is an agent skill from codeaholicguy/ai-devkit. 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.
Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Testing & QA, covering Test coverage and Test generation. The repository describes itself as: The control plane for AI coding agents. The licence is Apache-2.0.
When your agent uses it
- The user wants to write tests
- Update testing docs
- Close coverage gaps
- Run dev-lifecycle phase 8
Example prompts
- “/dev-testing”
Requirements
- Node.js
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Run npx ai-devkit@latest lint before phase work.
- If working on a named feature, run npx ai-devkit@latest lint --feature .
- 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.
What it can do on your machine
Read from SKILL.md and the folder at commit 7ef0cd5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dev Testing loads about 482 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 245 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from codeaholicguy/ai-devkit at commit 7ef0cd5, republished under its Apache-2.0 licence (© codeaholicguy). 245 words, ~482 tokens.
Download SKILL.mdSave it as
.claude/skills/dev-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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
- Run
npx ai-devkit@latest lintbefore 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
verifyskill before making coverage or test-pass claims. - If parent
dev-lifecycleestablished usable task tracing, emit testing phase, next-action, and evidence events pertask.
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.jsonpaths.docs, falling back todocs/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.
© codeaholicguy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/dev-testing of codeaholicguy/ai-devkit.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 7ef0cd5
Compare with similar skills
Dev Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dev Testing this skillcodeaholicguy/ai-devkit | 1.6k | — | ~482 | Automated safety check: Pass | Apache-2.0 | |
| E2E Test ThinkerUniClipboard/UniClipboard | 1.8k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Ralph Coveragejvm-skills/jvm-skills | 140 | — | ~683 | Automated safety check: Pass | Apache-2.0 | |
| Designing TestsCloudAI-X/opencode-workflow | 275 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Mutation Testingproffesor-for-testing/agentic-qe | 494 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Write Testsgnomeria/usbtree | 688 | — | ~622 | Automated safety check: Pass | MIT |
Similar skills
Ralph Coverage
jvm-skills/jvm-skills
Run Ralph in coverage mode — iteratively write tests for untested classes until coverage targets are met.
Designing Tests
CloudAI-X/opencode-workflow
Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.
Mutation Testing
proffesor-for-testing/agentic-qe
Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.
Write Tests
gnomeria/usbtree
Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression.
Mutation Test
jmagly/aiwg
Run mutation testing to validate test quality beyond code coverage.
More from codeaholicguy/ai-devkit
All 28 skills in this repoAgent Management
codeaholicguy/ai-devkit
AI DevKit · Manage running AI agents with ai-devkit agent commands.
Dev Lifecycle
codeaholicguy/ai-devkit
AI DevKit · Orchestrator for structured SDLC phase skills. An agent skill from codeaholicguy/ai-devkit.
Task
codeaholicguy/ai-devkit
AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI.
Simplify Implementation
codeaholicguy/ai-devkit
AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability.
Agent Communication
codeaholicguy/ai-devkit
AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send.
Technical Writer
codeaholicguy/ai-devkit
AI DevKit · Review and improve documentation for novice users.
Related
Categories
Questions about Dev Testing
What does Dev Testing do?
AI DevKit · Testing phase guidance for adding and validating feature test coverage. Dev Testing is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Testing phase guidance for adding and validating feature test coverage.
When should I use Dev Testing?
Dev Testing fits situations like: the user wants to write tests; update testing docs; close coverage gaps; run dev-lifecycle phase 8.
How do I install Dev Testing in Claude Code?
Run `npx skills add codeaholicguy/ai-devkit --skill dev-testing -a claude-code`. Or copy the skill folder (skills/dev-testing in codeaholicguy/ai-devkit) into .claude/skills/dev-testing in your project. Claude Code loads it when a task matches its description.
How do I install Dev Testing in Codex?
Run `npx skills add codeaholicguy/ai-devkit --skill dev-testing -a codex`. Or copy the skill folder (skills/dev-testing in codeaholicguy/ai-devkit) into .agents/skills/dev-testing in your project. Codex loads it when a task matches its description.
Can I use Dev Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codeaholicguy/ai-devkit --skill dev-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-testing, .gemini/skills/dev-testing, .github/skills/dev-testing and .opencode/skills/dev-testing in your project.
What does Dev Testing need to run?
Going by SKILL.md and its folder, Dev Testing needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Dev Testing access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Dev Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dev Testing use?
Dev Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dev Testing use?
About 482 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dev Testing?
Skills that share tags, products or a category with Dev Testing: E2E Test Thinker (UniClipboard/UniClipboard, 1.8k stars), Ralph Coverage (jvm-skills/jvm-skills, 140 stars), Designing Tests (CloudAI-X/opencode-workflow, 275 stars) and Mutation Testing (proffesor-for-testing/agentic-qe, 494 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dev Testing?
codeaholicguy (a GitHub user) maintains it in codeaholicguy/ai-devkit, which has 1,641 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.
Source: codeaholicguy/ai-devkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.