code-testing-extensions

Provides file paths to language-specific extension files for the code-testing pipeline. Call this skill to discover available extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Do not use directly — invoked by code-testing agents and skills that need language-specific references.

Ir para a instalação

Repositório: dotnet/skills
Última atividade na origem: 12 de agosto de 2026 às 15:38
Idioma detectado do SKILL.md: inglês
Estrelas: 5.190
Forks: 387

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/dotnet/skills --skill code-testing-extensions

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

22 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

convert-to-cpm

Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.

2026-08-14

technology-selection

Guides technology selection and implementation of AI and ML features in .NET 8+ applications using ML.NET, Microsoft.Extensions.AI (MEAI), Microsoft Agent Framework (MAF), GitHub Copilot SDK, ONNX Runtime, and OllamaSharp. Covers the full spectrum from classic ML through modern LLM orchestration to local inference. Use when adding classification, regression, clustering, anomaly detection, recommendation, LLM integration (text generation, summarization, reasoning), RAG pipelines with vector search, agentic workflows with tool calling, Copilot extensions, or custom model inference via ONNX Runtime to a .NET project. DO NOT USE FOR projects targeting .NET Framework (requires .NET 8+), the task is pure data engineering or ETL with no ML/AI component, or the project needs a custom deep learning training loop (use Python with PyTorch/TensorFlow, then export to ONNX for .NET inference).

2026-08-14

code-testing-agent

Generate or add unit tests for existing code, from one function to a complete project-wide suite. ALWAYS USE when asked to "write unit tests", "add tests", "generate tests", "cover this untested method", scaffold tests where none exist, or create comprehensive tests across multiple modules or packages. Polyglot: C#/.NET, Python/pytest, TS/JS, Go, Rust, Java, Ruby. Handles classic non-SDK/packages.config MSTest projects, explicit Compile registration, sparse workspaces, existing-suite extension, and proportional focused work. DO NOT USE for only running/diagnosing tests, analyzing a coverage report, auditing test quality, or answering an MSTest API question without writing tests.

2026-08-12

Ver todas deste repositório

Code Testing Extensions

This skill provides access to language-specific guidance files used by the code-testing pipeline. Call this skill to get the file paths, then read the relevant file for your target language.

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 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

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 extension file for the target language before writing test code. When an <language>-examples.md file exists for the target language, read it alongside the base extension to see a concrete end-to-end pipeline walkthrough (research output, plan, generated tests, fix cycles, final report).

Code Testing Extensions

This skill provides access to language-specific guidance files used by the code-testing pipeline. Call this skill to get the file paths, then read the relevant file for your target language.

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 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

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

name	code-testing-extensions
description	Provides file paths to language-specific extension files for the code-testing pipeline. Call this skill to discover available extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Do not use directly — invoked by code-testing agents and skills that need language-specific references.
user-invocable	false
disable-model-invocation	true
license	MIT

name	code-testing-extensions
description	Provides file paths to language-specific extension files for the code-testing pipeline. Call this skill to discover available extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Do not use directly — invoked by code-testing agents and skills that need language-specific references.
user-invocable	false
disable-model-invocation	true
license	MIT

code-testing-extensions

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório