900 skills · sorted by relevance
Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.
Write and improve C# unit tests with MSTest 3.x/4.x. Covers assertions that check expected results, tests with multiple input sets, asynchronous setup, cleanup, and test organization, with guidance on APIs that differ between versions.
Write C# unit tests with NUnit using clear naming, focused assertions, and independent test cases. Covers project setup, testing with multiple input values, exception checks, and replacing dependencies with mocks to test components in isolation.
Match C# and .NET tasks to the appropriate specialist skill using the request and project evidence. Invoke available specialists, explain how to obtain missing plugins, and complete suitable tasks with standard tooling when possible.
Diagnose why an existing skill fails evaluations or shows no clear improvement. Separate content problems from test data, execution failures, activation issues, and insufficient evaluation tasks, then apply targeted fixes and validate them.
Create Vally evaluation specifications for skills, custom agents, and workflow packages. Design distinct test requests, prepare fixture files, define automated checks and outcome rubrics, and size comparisons to provide meaningful evidence without favoring the skill’s wording.
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.
Install a .NET SDK, the tools used to build .NET projects, inside a project folder. Configure version selection and shared setup scripts to test previews or reproduce team and CI environments without changing the system installation.
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.
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.
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.
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.
Provide language-specific reference files for test analysis skills. The catalog helps agents recognize test methods, assertions, skipped tests, waiting patterns, setup and cleanup hooks, external dependencies, and tagging capabilities across different frameworks.
Create a missing .NET test project or repair references and solution registration in an existing one. Follow the repository’s framework and package conventions, then verify the build or test entry point used by CI, the automated integration process.
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.
Refactor C#/.NET code through renaming, extraction, consolidation, and other structural changes while preserving behavior. Check compatibility beyond code references, including public APIs and serialized names, then validate with builds and relevant tests.
Diagnose slow MSBuild startup by measuring project evaluation, the work done before compilation. Inspect logs for costly file searches, imported configuration, and repeated evaluations, then identify targeted changes supported by timing evidence.
Run small C# apps without creating a project, using the .NET CLI, its command-line tool. Use it to test language features, explore APIs, or prototype utilities with helper files and NuGet packages.
Build or update ASP.NET Core API endpoints with defined request and response types, appropriate HTTP status codes, OpenAPI documentation, and centralized error handling. Also creates .http request files for manually checking endpoint behavior.
Write and review .NET calls to native C/C++ libraries using P/Invoke. Covers function declarations, string conversion, memory ownership, and platform differences to help investigate crashes, memory leaks, and corrupted data.
Add, review, or fix calls between Blazor and JavaScript. Organize JavaScript modules alongside components, control when calls run, combine related operations, and clean up references with handling for server disconnections.
Generate ASP.NET Core pages, components, or API endpoints for creating, reading, updating, and deleting database records. Follow the project's existing styling and code conventions, with database migrations and verification of the generated functionality.
Diagnose MSBuild failures from an existing binary build log. Inspect errors, settings, project references, and execution details to explain failures that console output alone does not clarify, including failures across multiple projects.
Diagnose and fix .NET MAUI development environment problems involving SDKs, Java, Android tools, and platform requirements. The skill discovers required versions from NuGet metadata and checks the environment again after each fix.