code-testing-agent
MANDATORY ENTRY POINT for generating or writing tests. Invoke this skill before editing files whenever the user asks to generate tests, write/add unit tests, scaffold a test project or suite, improve/achieve coverage, extend an existing suite to cover an untested method, or test an app, API, service, module, library, or package. Applies to a single function, method or file as much as to a whole project — scope changes how much of the workflow runs, never whether the skill applies. Invoke it when the workspace looks sparse, gutted or partially deleted — then test only the source that remains an
npx skills add dotnet/skills --skill code-testing-agent --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.
# Code Testing Generation Skill An AI-powered skill that generates comprehensive, workable unit tests for any programming language using a coordinated multi-agent pipeline. ## When to Use This Skill Use this skill when you need to: - Generate unit tests for an entire project or specific files - Improve test coverage for existing codebases - Create test files that follow project conventions - Write tests that actually compile and pass - Add tests for new features or untested code ## When Not to Use - Running or executing existing tests (use the `run-tests` skill) - Migrating between test frameworks (use migration skills) - Writing tests specifically for MSTest patterns (use `writing-mstest-tests`) - Debugging failing test logic ## How It Works This skill coordinates multiple specialized agents in a **Research → Plan → Implement** pipeline: ### Pipeline Overview ```text ┌─────────────────────────────────────────────────────────────┐ │ TEST GENERATOR │ │ Coordinates the full pipeline and manages state │ └─────────────────────┬───────────────────────────────────────┘ │ ┌─────────────┼─────────────┐ ▼ ▼ ▼ ┌───────────┐ ┌───────────┐ ┌───────────────┐ │ RESEARCHER│ │ PLANNER │ │ IMPLEMEN
- When to Use This Skill
- When Not to Use
- How It Works
- Pipeline Overview
- Step-by-Step Instructions
- Step 1: Determine the user request
- Step 2: Size the request before invoking anything
- Step 3: Invoke the Test Generator (broad scope)
- Step 4: Execute with bounded context
- Completion contract
- State Management
- Agent Reference
- Requirements
- Troubleshooting
What does the code-testing-agent skill do?
MANDATORY ENTRY POINT for generating or writing tests. Invoke this skill before editing files whenever the user asks to generate tests, write/add unit tests, scaffold a test project or suite, improve/achieve coverage, extend an existing suite to cover an untested method, or test an app, API, service, module, library, or package. Applies to a single function, method or file as much as to a whole project — scope changes how much of the workflow runs, never whether the skill applies. Invoke it when the workspace looks sparse, gutted or partially deleted — then test only the source that remains an
How do I install it?
Run `npx skills add dotnet/skills --skill code-testing-agent --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 dotnet/skills, a repository with 4,927 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.