code-testing-extensions

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

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/Netcodr81/kinetic-reports --skill code-testing-extensions-netcodr81
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-testing-extensions
Source: https://github.com/Netcodr81/kinetic-reports/tree/main/.github/skills/code-testing-extensions
Command: npx skills add https://github.com/Netcodr81/kinetic-reports --skill code-testing-extensions-netcodr81

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated test generation agents need accurate, language-specific knowledge about build commands, test frameworks, mocking patterns, and common errors. This Skill centralizes that guidance into per-language extension files so code-testing agents can load exactly the reference material they need for the target language instead of guessing commands or frameworks. ## Core Features & Use Cases - Language Extension Files: Provides dedicated guidance files for .NET, Python, TypeScript/JavaScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin, covering build/test commands, framework detection, mocking rules, and common error fixes. - End-to-End Pipeline Examples: Ships concrete example files (e.g., dotnet-examples.md, go-examples.md) showing sample research output, plans, generated test files, fix cycles, and final reports for the test generation pipeline. - Use Case: A code-testing agent targeting a Go repository invokes this Skill, reads extensions/go.md to learn idiomatic table-driven test patterns and go test command flags, then reads go-examples.md to model its research, plan, and final report output. ## Quick Start Invoke this Skill and read the extension file matching your target language, such as extensions/java.md for a Java project, before writing any test code.

Frequently Asked Questions about code-testing-extensions

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

FAQPage Schema
How do I get language-specific test generation guidance for my project?▼

Invoke this Skill to receive the available extension file paths, then read the file matching your target language, such as extensions/go.md for Go or extensions/java.md for Java. Each file contains build commands, test commands, framework detection rules, and mocking guidelines.

What languages does the code-testing pipeline support?▼

Extension files cover .NET (C#/F#/VB), Python, TypeScript/JavaScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin. Several languages also include example files showing a full pipeline walkthrough from research to final report.

Should I read the examples file alongside the base extension file?▼

Yes. When a <language>-examples.md file exists for your target language, read it alongside the base extension. It shows concrete research output, a plan, generated tests, fix cycles, and a final report for that language's pipeline.

Can I invoke this Skill directly as an end user?▼

No. The Skill is marked user-invocable: false and disable-model-invocation: true, meaning it is designed to be called internally by code-testing agents and skills that need language-specific references, not used standalone.

Why do generated tests fail with framework or build errors?▼

Each extension file documents common errors and fixes, such as missing project references in .NET (CS0234/CS0246), unanchored -run regexes in Go, or missing coverage link flags in C++. Consult the Common Errors table in the relevant extension file before retrying.