code-testing-extensions

Provides file paths to language-specific test generation guidance files for the code-testing pipeline.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/Patrick-Rex/DotNetTechSamples --skill code-testing-extensions-patrick-rex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-testing-extensions
Source: https://github.com/Patrick-Rex/DotNetTechSamples/tree/main/.agents/plugins/dotnet-test/skills/code-testing-extensions
Command: npx skills add https://github.com/Patrick-Rex/DotNetTechSamples --skill code-testing-extensions-patrick-rex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Test generation agents need language-specific build commands, test commands, framework conventions, and error fixes, but embedding all of that in one prompt is impractical. This Skill acts as a discovery index that points agents to the correct per-language extension file before they write any test code. ## Core Features & Use Cases - Language Extension Index: Maps 11 languages (.NET, Python, TypeScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, Kotlin) to dedicated guidance files covering build/test commands, framework detection, mocking rules, and common errors. - Pipeline Examples: Provides end-to-end worked examples (research output, plan, generated tests, fix cycles, final report) for .NET, Python, TypeScript, Go, Java, and C++. - Use Case: A code-testing agent about to generate tests for a Go repository calls this Skill, reads extensions/go.md for table-driven test conventions and go test command syntax, then reads go-examples.md to model its research and plan output. ## Quick Start Ask the agent to load the extension guidance file for your target language before generating any tests.

Frequently Asked Questions about code-testing-extensions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right test generation guidance for my programming language?

Call this Skill to get the path to the extension file matching your language, such as extensions/dotnet.md for .NET or extensions/go.md for Go. Then read that file before writing any test code to get the correct build commands, framework conventions, and error fixes.

What languages does the code-testing pipeline support?

The pipeline provides extension guidance for .NET (C#/F#/VB), Python, TypeScript/JavaScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin. Several languages also have companion example files showing full pipeline walkthroughs.

Should I read the examples file in addition to the base extension file?

Yes, when a <language>-examples.md file exists for your target language, read it alongside the base extension. The examples show concrete end-to-end pipeline output including research, plan, generated tests, fix cycles, and the final report.

Can I invoke this Skill directly as a user?

No, this Skill is marked as not user-invocable and has model invocation disabled. It is called internally by code-testing agents and skills that need language-specific reference material during test generation.

Why does the .NET extension say to run dotnet sln add after creating a test project?

A new test .csproj is invisible to solution-level dotnet test commands and CI harnesses until registered with dotnet sln add. The extension mandates this step and a harness-equivalent discovery check so generated tests are actually enumerated and executed.