code-testing-extensions

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

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/adinj00/player-performance --skill code-testing-extensions-adinj00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-testing-extensions
Source: https://github.com/adinj00/player-performance/tree/main/.agents/skills/code-testing-extensions
Command: npx skills add https://github.com/adinj00/player-performance --skill code-testing-extensions-adinj00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated test generation agents need accurate, language-specific build commands, test framework conventions, mocking patterns, and error fixes. This Skill centralizes that guidance so code-testing agents can load the right reference file for the target language instead of guessing commands or frameworks. ## Core Features & Use Cases - Language Extension Files: Reference documents for .NET, Python, TypeScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin covering build/test commands, framework detection, mocking rules, and common errors. - End-to-End Pipeline Examples: Concrete walkthroughs for .NET, Python, TypeScript, Go, Java, and C++ showing research output, plans, generated test files, fix cycles, and final reports. - Use Case: A code-testing agent targeting a Go repository reads go.md to learn table-driven test conventions, go test -run regex anchoring, and interface-based fakes, then reads go-examples.md to mirror a complete pipeline run. ## Quick Start Ask the code-testing agent to load the extension file matching your project's 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 generate tests for a Go project with an AI agent?

Load the Go extension file to get `go test` commands, table-driven test patterns, and interface-based mocking guidance. The companion go-examples.md shows a full pipeline run including research output, plan, generated test file, and fix cycles.

What test frameworks does the code-testing pipeline support?

The extension files cover MSTest, xUnit, and NUnit for .NET; pytest for Python; Jest, Vitest, and Mocha for TypeScript; GoogleTest and Catch2 for C++; JUnit 4/5 and TestNG for Java; Pester for PowerShell; plus standard tooling for Go, Rust, Ruby, Swift, and Kotlin.

How do I fix CS0246 or CS0234 errors in generated .NET tests?

These errors mean the test project is missing a ProjectReference to the source assembly. The dotnet.md extension instructs adding a ProjectReference entry to the test .csproj and registering new test projects with dotnet sln add.

Does the pipeline support C++ coverage instrumentation?

Yes, the C++ extension documents target-scoped gcov-compatible coverage flags for CMake, plus gcovr, llvm-cov, and lcov collection commands. It requires adding --coverage to both compile and link flags for the test and library targets.

When should the language examples files be read?

Read the <language>-examples.md file alongside the base extension when one exists for the target language. It shows a concrete end-to-end walkthrough: research output, implementation plan, generated tests, fix cycles, and the final report.