Skip to main content
skill CX Codex

code-testing-extensions — Claude Code skill: language testing catalog

code-testing-extensions is a Claude Code skill that maps paths to code-testing guidance files, which agents read directly.

MIT 4,600 installs ★ 6,320 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dotnet/skills --skill code-testing-extensions -a claude-code
Open on GitHub

What code-testing-extensions does

The skill lists bundled guidance files for testing in .NET, Python, TypeScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin. Each file covers build and test commands, common errors, and templates for a specific framework.

Separate example files walk through a full pipeline: research, plan, generated test, fix cycles, final report. They exist for .NET, Python, TypeScript, Go, and Java. Paths are relative to the catalog itself, not the project workspace.

This is a reference-only catalog. Agents and other skills read its files directly; the model's skill tool must not invoke it. Load an example file only when the repository has no representative tests and the base extension does not resolve the pattern.

What it helps with

  • locate test commands for pytest, Jest, Maven, Gradle, cargo test or go test
  • look up common testing errors for a specific language
  • get a test template for MSTest, JUnit 5 or Pester v5
  • follow a complete test generation and fix cycle from an example file
  • handle mocking specifics in Java, Go, Ruby or Kotlin

Example prompts for the agent

  • Read extensions/go.md and write a table-driven test for this function
  • Check extensions/java.md and add a Mockito test for the Spring Boot service
  • Open extensions/python-examples.md for a full test fix cycle example

How to install code-testing-extensions

1Skills CLI (Vercel)

npx skills add dotnet/skills --skill code-testing-extensions -a claude-code

2Manually: put the files in place

~/.claude/skills/code-testing-extensions/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/code-testing-extensions/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about code-testing-extensions

How do I install code-testing-extensions in Claude Code?

Run npx skills add dotnet/skills --skill code-testing-extensions -a claude-code. The skill lands at ~/.claude/skills/code-testing-extensions/SKILL.md.

What does code-testing-extensions do?

It is a reference catalog of language-specific testing guidance files. Agents read the relevant file directly; the catalog must not be invoked through the model.

When should I load the example files?

Only when the repository has no representative tests and the base extension does not cover the pattern you need. Skip them for focused requests with established local conventions.

Source text

SKILL.md · MIT
---
name: code-testing-extensions
description: >-
  Provides file paths to language-specific extension files for the code-testing
  pipeline. Read this reference-only catalog for extension guidance files
  (e.g., dotnet.md for .NET, cpp.md for C++). Agents and skills read its bundled
  files directly; do not invoke this catalog through the model's skill tool.
user-invocable: false
disable-model-invocation: true
license: MIT
---

# Code 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](extensions/dotnet.md) | .NET (C#/F#/VB) | Build commands, test commands, project reference validation, common CS error codes, MSTest template |
| [extensions/python.md](extensions/python.md) | Python | Framework-adaptive test commands (pytest, custom runners), project layout detection, mocking guidelines, common errors |
| [extensions/typescript.md](extensions/typescript.md) | TypeScript/JavaScript | Build/test commands (Jest/Vitest/Mocha), framework detection, mocking, TS-specific considerations |
| [extensions/powershell.md](extensions/powershell.md) | PowerShell | Test commands (Pester v5), module import patterns, discovery/run pitfalls, mocking, common errors |
| [extensions/cpp.md](extensions/cpp.md) | C++ | Testing internals with friend declarations |
| [extensions/go.md](extensions/go.md) | Go | `go test` commands, table-driven tests, integration vs unit layout, mocking via interfaces, common errors |
| [extensions/java.md](extensions/java.md) | Java | Maven/Gradle commands, JUnit 4/5 and TestNG detection, Mockito, Spring Boot slices, common errors |
| [extensions/rust.md](extensions/rust.md) | Rust | `cargo test` commands, unit vs integration vs doc tests, features, async test harnesses, common errors |
| [extensions/ruby.md](extensions/ruby.md) | Ruby | RSpec and Minitest commands, Bundler usage, Rails specifics, mocking patterns, common errors |
| [extensions/swift.md](extensions/swift.md) | Swift | SPM and Xcode test commands, XCTest vs Swift Testing, `@testable import`, async/throws tests, common errors |
| [extensions/kotlin.md](extensions/kotlin.md) | Kotlin | Gradle commands, JUnit/Kotest detection, MockK, coroutines test, KMP and Android specifics, common errors |
| [extensions/dotnet-examples.md](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](extensions/python-examples.md) | Python | Concrete pipeline examples (pytest): research, plan, generated test file, fix cycles, final report |
| [extensions/typescript-examples.md](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](extensions/go-examples.md) | Go | Concrete pipeline examples (standard `testing`): research, plan, table-driven test file, fix cycles, final report |
| [extensions/java-examples.md](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.

© dotnet · MIT · dotnet/skills

Similar skills

All skills for Testing and QA →

From the same set109

The whole set →
directory-build-organization directory-build-organization — a skill that decides what belongs in Directory.Build.props, .targets and .rsp, so several projects stop repeating the same MSBuild policy. CX Codex +1 4,800installs test-gap-analysis test-gap-analysis maps which caller-visible production outcomes could change without any existing test failing. Useful before you trust a suite to guard a change. CX Codex +1 4,700installs assertion-quality assertion-quality is a Claude Code skill that reviews assertions in existing tests. It activates for requests about shallow, trivial, or overly similar checks. CX Codex +1 4,700installs binlog-failure-analysis binlog-failure-analysis diagnoses MSBuild build failures from .binlog files. Use it when console output is unclear or cascading errors break multi-project builds. CX Codex +1 4,700installs binlog-generation The binlog-generation skill makes your agent add /bl:{} to every MSBuild command, so each build leaves a .binlog with a full trace you can inspect after a failure or a slowdown. CX Codex +1 4,600installs dotnet-pinvoke dotnet-pinvoke calls C and C++ native libraries from .NET via DllImport and LibraryImport. Helps map signatures accurately, configure string marshalling, and prevent memory corruption. CX Codex +1 4,600installs build-perf-diagnostics build-perf-diagnostics — a skill for Claude Code examines MSBuild build logs and timing summaries to locate slow targets and tasks. Use it to investigate a build slowdown after collecting a baseline. CX Codex +1 4,600installs crap-score Calculates Change Risk Anti-Patterns (CRAP) scores for .NET methods, classes, and files. It highlights complex code that lacks adequate test coverage. CX Codex +1 4,600installs

Project sponsors

Companies that keep this analytics open