@dotnet
Organization
Home of the open source .NET platform
112 skills1 repository 5.7K
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.
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.
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.
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.
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.
Upgrade an existing .NET 8 project to .NET 9 by addressing build errors and compatibility changes. Update related packages, containers, and build pipelines, then verify the migration with clean builds and tests.
Apply the System.Text.Json APIs introduced in .NET 11 to produce PascalCase JSON names and retrieve typed serialization metadata, the information used to convert objects. Create runnable examples and check metadata availability without exception-based probing.
Fill in related settings for .NET project creation while preserving explicit user choices. Produce a table explaining each choice and an exact dotnet new command, checking available options against the selected template’s help.
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.
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.
Diagnose and fix MSBuild property problems, including overwritten settings, ineffective conditions, and environment-dependent paths. Review defaults, list appending, and evaluation order so project files and shared build settings retain the intended values.
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.
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.
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.
Analyze MSBuild binary logs and timing summaries to find why builds are slow. Identify costly reference resolution, code analysis, file copying, restore work, or serialized tasks, then prioritize improvements by their share of total build time.
Review and fix how MSBuild manages lists of files and their metadata, or attached information. Check Include, Remove, Update, filtering, path transformations, duplicates, and execution grouping to clarify whether item operations behave as intended.
Plan and implement complex Blazor pages by dividing them into focused components. Define parent and child relationships, decide where data is managed, map data and events between components, and establish the order for building them.
Connect .NET MAUI screens to application data using XAML or C#. Covers compile-time binding checks, change notifications, value conversion, and fallback displays to help implement bindings and investigate screens that fail to update.
Build page navigation in .NET MAUI apps using Shell. Configure tabs and slide-out menus, register page routes, pass data between pages, and add confirmation dialogs before users leave a page.
Create or review Blazor components, reusable parts of a web interface. Covers passing data and events between parent and child components, content templates, asynchronous work, display states, and resource cleanup when components are removed.
Set up Ignite UI Lite controls or GridLite in Blazor applications. Match package references, service registration, namespaces, theme stylesheets, and interactive rendering settings to the app’s structure, including projects with separate server and client code.
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.
Plan initialization, state saving, restoration, and cleanup around .NET MAUI app lifecycle events. Understand how Window events map to each platform, distinguish lost focus from backgrounding, and account for multiple windows.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)