111 skills (repositories by dotnet) · sorted by popularity
Migrate legacy .NET project files to SDK-style format, reducing repetitive XML and explicit file lists. Convert package references, move assembly metadata into project settings, and consolidate shared build and package settings across multiple projects.
Prepare .NET projects for Native AOT, compilation before execution, and trimming, which removes unused code. Use build warnings to guide type annotations, reflection changes, and source-generated JSON serialization, then check all target frameworks.
Compare two or more dotnet new templates using their installed options, features, and supported frameworks. Get a focused comparison table and a recommendation that explains which template best fits the project you want to build.
Find changes in observable behavior that existing tests could miss. Map public results to test assertions, identify gaps in boundaries, permissions, and calculations, and propose focused tests, with optional verification when requested.
Scan C# code for dependencies on clocks, files, environment settings, and other resources that make tests difficult. Get source locations, consistent counts, and suggested abstractions, interfaces or providers that let tests control those dependencies.
Classify existing tests with standard tags for success cases, errors, boundaries, and other behaviors. Get a per-test mapping and distribution summary, or apply tags using supported framework syntax and verify compilation and test discovery.
Move .NET tests from VSTest to Microsoft.Testing.Platform, the test execution platform. Update project settings, test commands, and CI pipelines for the selected SDK, then verify test counts and expected reports or diagnostic files.
Keep older instructions working by forwarding explicit calls under the former name to code-testing. This compatibility alias passes along the original request and follows that skill’s workflow without adding another interpretation step.
Replace C# static calls for time, files, or environment values with existing abstractions that tests can substitute. Update construction and affected tests within a defined scope, while preserving read counts, evaluation order, date-time semantics, and existing static callers.
Find language-specific guidance files for a code-testing pipeline. This reference catalog points agents to build and test commands, mocking patterns, common errors, and selected workflow examples across languages including .NET, Python, TypeScript, Go, and Java.
Review custom dotnet new templates before publishing. Check required fields, parameter types and defaults, command name conflicts, and constraints, then receive findings grouped by severity with concrete fixes for errors and warnings.
Calculate change risk for a specific .NET method, class, or file by combining code complexity with measured test coverage. Get ranked results and recommendations on where to add tests or simplify logic.
Identify a .NET project’s test framework, project format, and execution platform: VSTest or Microsoft.Testing.Platform. Trace configuration imports and overrides to explain the result, including conflicting settings or differences between target frameworks.
Create .NET projects from templates and align them with neighboring projects and centralized package versions. Validate options, connect projects in a solution, and build the result to check that the generated structure works.
Find suitable .NET project templates from a plain-language project description. Inspect available options, defaults, and requirements, then preview generated files without creating them. Receive a concrete template recommendation with relevant parameters and any required installation details.
Correct and improve existing MSTest tests using APIs supported by the installed version. Refine assertions and failure messages, update data-driven tests, fix setup and cleanup, and address MSTest diagnostics while preserving the project's established conventions.
Investigate MSBuild failures, measure slow builds, or review existing build definitions. Use binary logs, project settings, and comparable timing measurements to identify causes, propose focused repairs, and verify behavior without broad configuration changes.
Migrate .NET tests from xUnit.net v2 to v3 while preserving the existing test runner. Update packages, project settings, and affected test code, then verify test discovery, execution, and skip behavior.
Move NuGet package versions from individual .NET projects into a shared management file. The skill audits version conflicts, preserves project conditions, validates builds before and after conversion, and produces comparison files and a migration report.
Upgrade MSTest v3 test projects to v4 by updating packages, adapting code to changed APIs, and checking execution behavior. It also helps resolve build errors and problems finding tests in CI after an upgrade.
Make C# code testable when it directly uses static services such as time, files, or processes. It introduces existing abstractions or minimal wrappers, supplies dependency registration, and demonstrates tests with controlled substitutes for real resources.
Provide reference syntax for selecting .NET tests by name, class, category, or other properties. Help test-running skills construct filters for VSTest and Microsoft Testing Platform, or translate existing filters for a different test framework.
Convert .NET tests from xUnit.net v2 or v3 to MSTest v4 while keeping the existing test runner and target framework. Preserve assertions, shared setup, and parallel execution, then compare test counts and outcomes.
Interpret MSBuild performance summaries when ResolveProjectReferences appears unusually expensive. Separate time spent waiting for dependent projects from actual task work, then use task self-time rankings to identify a concrete optimization target.