code-testing-extensions

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

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/D1ssolve/craft-agents --skill code-testing-extensions-d1ssolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-testing-extensions
Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/code-testing-extensions
Command: npx skills add https://github.com/D1ssolve/craft-agents --skill code-testing-extensions-d1ssolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When writing tests across multiple programming languages, agents need language-specific build commands, test frameworks, and error patterns. This Skill centralizes discovery of per-language extension guidance files so code-testing agents can locate the right reference before generating tests. ## Core Features & Use Cases - Language Extension Discovery: Returns file paths to guidance files for .NET, Python, TypeScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin. - Pipeline Examples: Provides end-to-end example files (research, plan, generated tests, fix cycles, final report) for .NET, Python, TypeScript, Go, and Java. - Use Case: A code-testing agent targeting a Java project calls this Skill, receives the path to extensions/java.md, reads it for Maven/Gradle commands and JUnit 5 detection rules, then generates tests aligned with the project's framework. ## Quick Start Ask the agent to get the extension guidance file for your target language, for example request the Java testing extension file before writing JUnit 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 language-specific test guidance for the code-testing pipeline?

Call this Skill to receive file paths to extension files such as extensions/java.md or extensions/python.md. Then read the file matching your target language to get build commands, test framework detection rules, and common error patterns.

What languages are supported by the code-testing extension files?

Extension files cover .NET (C#/F#/VB), Python, TypeScript/JavaScript, PowerShell, C++, Go, Java, Rust, Ruby, Swift, and Kotlin. Each file documents framework-specific test commands, mocking approaches, and common errors.

Which languages have end-to-end pipeline examples?

Concrete pipeline examples exist for .NET, Python, TypeScript, Go, and Java. Each examples file walks through research output, plan, generated test files, fix cycles, and the final report.

Should I call code-testing-extensions directly as an end user?

No, this Skill is designed to be invoked by code-testing agents and other skills that need language-specific references. It acts as a discovery layer returning file paths rather than performing test generation itself.

When should I read the examples file alongside the base extension?

Read the language-examples.md file alongside the base extension whenever one exists for your target language. It shows a concrete end-to-end walkthrough of the testing pipeline, which helps calibrate the structure of generated tests and reports.