Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

code-testing-extensions

Estrellas3575

Forks266

Actualizado23 de junio de 2026, 09:03

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

dotnet

dotnet/skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

Explorador de archivos

22 archivos

SKILL.md

readonly

Más de este repositorio

mismo repositorio

dotnet-pinvoke

dotnet/skills

Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.

2026-06-293.6k

extension-points

dotnet/skills

Guide for MSBuild extensibility: CustomBefore/CustomAfter hooks, wildcard imports with alphabetic ordering, import gating with control properties, NuGet package build extension layout (build/buildTransitive), and the MicrosoftCommonPropsHasBeenImported guard. USE FOR: diagnosing and fixing MSBuild import and hook patterns, reviewing and fixing extension point anti-patterns in Directory.Build files, fixing missing Exists() guards on imports that break fresh clones, fixing NuGet package hooks being silently dropped instead of appended, making build targets extensible for other projects, injecting custom logic into the build pipeline, creating NuGet packages that extend the build, conditionally disabling imports. DO NOT USE FOR: target authoring patterns (use target-authoring), props vs targets placement (use directory-build-organization), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

2026-06-293.6k

msbuild-antipatterns

dotnet/skills

Catalog of MSBuild anti-patterns with detection rules and fix recipes. USE FOR: reviewing, auditing, or cleaning up .csproj, .vbproj, .fsproj, .props, .targets, or .proj files. Each anti-pattern has a symptom, explanation, and concrete BAD→GOOD transformation. Covers Exec-instead-of-built-in-task, unquoted conditions, hardcoded paths, restating SDK defaults, scattered package versions, and more. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake, etc.), project migration to SDK-style (use msbuild-modernization).

2026-06-293.6k

assertion-quality

dotnet/skills

Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow tests, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull / toBeTruthy()), flag self-referential or tautological assertions, measure assertion diversity, or audit whether tests verify different facets of behavior. Polyglot: .NET, Python, TS/JS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. DO NOT USE FOR: writing new tests (use code-testing-agent / writing-mstest-tests), mutation reasoning about whether tests would catch a bug (use test-gap-analysis), or a general severity-ranked anti-pattern audit (use test-anti-patterns), fixing or rewriting assertions, or writing, fixing, or modernizing MSTest tests, assertions, or attributes (use writing-mstest-tests).

2026-06-263.6k

test-anti-patterns

dotnet/skills

Audits an existing test file or suite in any language for anti-patterns and quality issues — produces a severity-ranked report (Critical/Warning/Info). INVOKE whenever asked to audit or review tests, find what's wrong with a suite, judge whether tests are any good, or check for: tests that pass but verify nothing, missing assertions, swallowed exceptions, self-comparing / tautological assertions, coverage-touching tests, broad exceptions, flaky or order-dependent tests (Thread.Sleep, DateTime.Now, shared state), duplicated tests, or magic values — in .NET, Python/pytest, TS/Jest, Java, Go, Ruby or C++. DO NOT USE FOR: writing new tests (use code-testing-agent, or writing-mstest-tests for MSTest); running tests (use run-tests); migration; assertion-diversity metrics (use assertion-quality); coverage/CRAP metrics (use coverage-analysis); the testsmells.org academic catalog (use test-smell-detection); fixing or modernizing MSTest tests, assertions, attributes, or lifecycle (use writing-mstest-tests).

2026-06-263.6k

coverage-analysis

dotnet/skills

Project-wide code coverage and CRAP (Change Risk Anti-Patterns) score analysis for .NET projects. Calculates CRAP scores per method and surfaces risk hotspots — complex code with low coverage that is dangerous to modify. Use to diagnose why coverage is stuck or plateaued, identify what methods block improvement, or get project-wide coverage analysis with risk ranking. USE FOR: coverage stuck, coverage plateau, can't increase coverage, what's blocking coverage, coverage gap, CRAP scores, risk hotspots, where to add tests, coverage analysis, coverage report. DO NOT USE FOR: targeted single-method CRAP analysis (use crap-score); auditing test code for coverage-touching or other anti-patterns (use test-anti-patterns); writing tests; running tests (use run-tests). Requires or produces coverage (Cobertura) and CRAP metrics.

2026-06-253.6k

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