code-testing-extensions skill
✓ VerifiedProvides a reference catalog of language-specific guidance files for code-testing pipelines.
- GitHub stars
- 5,942
- Files
- 22
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the code-testing-extensions skill do?
code-testing-extensions provides a reference catalog of language-specific guidance files for code-testing pipelines.
Summary generated from the skill's SKILL.md.
About the code-testing-extensions skill
Accessing language-specific guidance for automated testing pipelines is the primary function of this reference catalog. Developers use this resource to provide agents with the precise build commands, test runners, and mocking patterns required for various programming environments. Instead of relying on general knowledge, an agent loads specific files like dotnet.md or python.md to understand project layout detection, framework-adaptive commands, and common error codes.
This catalog serves as a directory of bundled files that agents read directly rather than through a tool invocation. It includes specialized documentation for languages such as Rust, Go, Java, and Swift, covering everything from cargo test commands to XCTest patterns. When a repository lacks existing test patterns, agents can also access language-specific example files to observe full cycles involving research, planning, and final reports.
What an agent can do with it
- 1Configure Python testing environmentsAn agent can retrieve framework-adaptive test commands and mocking guidelines for Python projects.
- 2Implement C++ testing internalsA developer can instruct an agent to use specific guidance for testing C++ internals using friend declarations.
- 3Generate Java test suitesAn AI client can use Maven or Gradle commands and Mockito patterns to build Java tests.
- 4Learn from testing workflowsWhen a repository has no existing tests, an agent can load example files to see complete research and fix cycles.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the code-testing-extensions skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the code-testing-extensions skill in Plugin
/plugin marketplace add dotnet/skills /plugin install dotnet-test@dotnet-agent-skills
Install the code-testing-extensions skill in Claude Code
~/.claude/skills/code-testing-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/code-testing-extensions ~/.claude/skills/code-testing-extensionsInstall the code-testing-extensions skill in Claude Code (project)
.claude/skills/code-testing-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/code-testing-extensions .claude/skills/code-testing-extensionsInstall the code-testing-extensions skill in Codex
~/.agents/skills/code-testing-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/code-testing-extensions ~/.agents/skills/code-testing-extensionsInstall the code-testing-extensions skill in Gemini CLI
~/.gemini/skills/code-testing-extensions/SKILL.md
$ npx degit dotnet/skills/plugins/dotnet-test/skills/code-testing-extensions ~/.gemini/skills/code-testing-extensionsInstall the code-testing-extensions skill in Claude.ai
npx degit dotnet/skills/plugins/dotnet-test/skills/code-testing-extensions code-testing-extensions && zip -r code-testing-extensions.zip code-testing-extensions # claude.ai → Customize → Skills → + → Create skill → Upload a skill → code-testing-extensions.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachabledotnet/skills/plugins/dotnet-test/skills/code-testing-extensions is public and reachablegithub.com/dotnet/skills/tree/HEAD/plugins/dotnet-test/skill ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/dotnet/skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-test/skill ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/dotnet/skills/blob/HEAD/plugins/dotnet-test/skill ↗Pass
SKILL.md
View on GitHubCode Testing Extensions
This reference-only catalog lists bundled guidance for the code-testing pipeline. Read the matching file directly; do not invoke this catalog as a skill. Resource paths are relative to this catalog, not the project workspace.
Available Extension Files
| File | Language | Contents |
|---|---|---|
| extensions/dotnet.md | .NET (C#/F#/VB) | Build commands, test commands, project reference validation, common CS error codes, MSTest template |
| extensions/python.md | Python | Framework-adaptive test commands (pytest, custom runners), project layout detection, mocking guidelines, common errors |
| extensions/typescript.md | TypeScript/JavaScript | Build/test commands (Jest/Vitest/Mocha), framework detection, mocking, TS-specific considerations |
| extensions/powershell.md | PowerShell | Test commands (Pester v5), module import patterns, discovery/run pitfalls, mocking, common errors |
| extensions/cpp.md | C++ | Testing internals with friend declarations |
| extensions/go.md | Go | go test commands, table-driven tests, integration vs unit layout, mocking via interfaces, common errors |
| extensions/java.md | Java | Maven/Gradle commands, JUnit 4/5 and TestNG detection, Mockito, Spring Boot slices, common errors |
| extensions/rust.md | Rust | cargo test commands, unit vs integration vs doc tests, features, async test harnesses, common errors |
| extensions/ruby.md | Ruby | RSpec and Minitest commands, Bundler usage, Rails specifics, mocking patterns, common errors |
| extensions/swift.md | Swift | SPM and Xcode test commands, XCTest vs Swift Testing, @testable import, async/throws tests, common errors |
| extensions/kotlin.md | Kotlin | Gradle commands, JUnit/Kotest detection, MockK, coroutines test, KMP and Android specifics, common errors |
| extensions/dotnet-examples.md | .NET (C#/F#/VB) | Concrete pipeline examples: sample research output, plan, generated tests, fix cycles, final report |
| extensions/python-examples.md | Python | Concrete pipeline examples (pytest): research, plan, generated test file, fix cycles, final report |
| extensions/typescript-examples.md | TypeScript/JavaScript | Concrete pipeline examples (Vitest, applicable to Jest): research, plan, generated test file, fix cycles, final report |
| extensions/go-examples.md | Go | Concrete pipeline examples (standard testing): research, plan, table-driven test file, fix cycles, final report |
| extensions/java-examples.md | Java | Concrete pipeline examples (JUnit 5 + Mockito on Maven): research, plan, generated test file, fix cycles, final report |
Usage
Read the appropriate base extension before writing test code. Load an
<language>-examples.md file only when the repository has no representative
tests and the base extension does not resolve the needed pattern. Do not load
end-to-end examples for a focused request with established local conventions.
Files in this skill
22code-testing-extensions skill questions
How do I install the code-testing-extensions skill in Claude Code?
Run npx degit dotnet/skills/plugins/dotnet-test/skills/code-testing-extensions ~/.claude/skills/code-testing-extensions. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the code-testing-extensions skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should I use this catalog?
This is a reference-only catalog; you should read the specific language files directly rather than invoking the catalog as a skill.
When should I load the example files?
Only load the language-specific example files if the repository lacks representative tests and the base extension file is insufficient.
What kind of information is included in the extension files?
The files contain build and test commands, framework detection, mocking guidelines, and common error codes for various programming languages.