.NET Platform

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a new .NET application from a template
• Combining an API, tests, and a library in one solution
• Adding a new project with centralized package versions

Choose and optionally run .NET test commands that match the project's SDK, test platform, and framework. Target specific tests, collect reports or diagnostics, and report execution results using syntax appropriate to the repository.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Getting an exact test command for a repository
• Running a specific class, category, or target framework
• Collecting TRX reports, coverage, or diagnostic logs

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing success-case and error-case test counts
• Adding standard tags to existing tests
• Reviewing the mix of boundary and integration tests

Convert NUnit 3 or 4 tests to MSTest v4 while keeping the existing target framework and test runner. The workflow translates assertions, test data, setup, and concurrency settings, then compares test counts and results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Migrating NUnit 3 or 4 tests to MSTest v4
• Preserving parameterized tests and test data
• Reviewing shared state and parallel execution during migration

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Following older instructions that use the former skill name
• Forwarding an explicit legacy call to code-testing
• Checking the distinction between skill and custom agent names

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether existing tests would catch a bug
• Find missing boundary and permission-denial tests
• Review exact amounts and rounding in financial calculations

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Convert legacy .csproj or .vbproj files to SDK-style
• Migrate packages.config to PackageReference
• Replace AssemblyInfo.cs with generated assembly metadata

Review existing tests using 19 research-backed test smell categories, meaning patterns that can weaken test quality. Get findings ranked by demonstrated risk, with precise code evidence and fixes suited to the test framework in use.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Request a test review using formal academic categories
• Prioritize test problems by their demonstrated risk
• Find causes of flaky tests or misleading passes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Making assertion failures easier to understand
• Correcting expected and actual argument order
• Improving existing data-driven tests

Create, modify, debug, and review Windows Forms applications while preserving their editable layouts in Visual Studio Designer. Covers resizing, data binding, asynchronous UI behavior, and checks that distinguish successful builds from actual screen and designer verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fixing forms that fail to open in Visual Studio Designer
• Resolving clipped controls after resizing or DPI changes
• Repairing bound lists that do not refresh

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrading a project from net8.0 to net9.0
• Resolving new build errors and warnings after upgrading
• Reviewing ASP.NET Core and EF Core behavior changes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Produce PascalCase JSON property names
• Convert dictionary keys to PascalCase
• Retrieve typed serialization metadata without casts

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding templates for an authenticated web API
• Checking installed and NuGet.org template choices
• Inspecting template parameters, defaults, and constraints

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix build settings overwritten by shared files
• Preserve existing compilation constants when adding new ones
• Correct conditions based on the target framework

Capture MSBuild execution records as binary logs during .NET builds, tests, packaging, publishing, or restores. It explains unique filenames, PowerShell quoting, and file checks so logs remain available for later failure or performance analysis.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving logs before investigating a build failure
• Keeping separate logs for Debug and Release builds
• Choosing log filenames for CI artifact uploads

Review database access built with Entity Framework Core to find slow queries, excessive database calls, memory costs, and correctness issues. It traces application code and uses available SQL logs or execution plans to support targeted fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing slow EF Core queries and excessive database calls
• Investigating memory use in imports and background jobs
• Checking search filters, pagination, and index coverage

Review C#/.NET code for about 50 inefficient API usage patterns across asynchronous work, memory, strings, collections, and I/O. Get exact occurrence counts, prioritized findings, and concrete fixes, with attention to frequently executed code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing frequently executed C#/.NET code
• Finding unnecessary memory allocations
• Checking known performance pitfalls before release

Turn .NET runtime addresses in Android crash reports into function names, source files, and line numbers. The skill extracts build identifiers, downloads matching debug symbols, and uses llvm-symbolizer to produce a readable backtrace.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Triaging native crashes in .NET MAUI or Mono Android apps
• Resolving libmonosgen-2.0.so and libcoreclr.so frames
• Investigating runtime-related SIGABRT or SIGSEGV crashes

Investigate .NET app crashes on Apple platforms by converting runtime addresses in .ips logs into function names, source files, and line numbers. It locates matching debug symbols and supports retrieving logs from connected iOS devices.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating .NET MAUI or Mono crashes on Apple platforms
• Resolving runtime addresses to source files and line numbers
• Retrieving crash logs from a connected iPhone

Analyze CLR activation logs to explain how .NET Framework selects and loads its runtime, the software that executes managed code. Diagnose loading failures, unexpected version choices, installation dialogs, and conflicting activation paths within a process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating failures to load the .NET Framework runtime
• Explaining why an unexpected CLR version was selected
• Tracing .NET 3.5 installation dialogs or their absence

Configure automatic crash dumps, files that capture application state, or collect one from a running modern .NET process. Follow platform and runtime guidance for desktop, server, Docker, or Kubernetes environments and receive the saved file location.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Enabling automatic dump collection when a .NET app crashes
• Capturing a dump from a running .NET process
• Setting up dump collection in Docker or Kubernetes

Design, configure, run, and review BenchmarkDotNet measurements of small .NET operations. Compare implementations, runtime versions, or input sizes, while controlling setup work, measurement errors, and case counts so results support a concrete performance decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Compare the performance of alternative implementations
• Reproduce a reported performance problem
• Measure performance before and after a code change

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a .NET MAUI development environment
• Investigating missing SDK or JDK build errors
• Checking the environment after SDK or OS updates

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving drafts and form inputs when an app enters the background
• Restoring state and refreshing data when an app resumes
• Choosing lifecycle events for initialization and cleanup