[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76SDQ52M2KBCHBXT43763S9":3,"skill-same:01M76SDQ52M2KBCHBXT43763S9":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M76SDQ52M2KBCHBXT43763S9","migrate-xunit-to-xunit-v3",null,"Migrates .NET test projects from xUnit.net v2 to xUnit.net v3. USE FOR: upgrading xunit to xunit.v3. DO NOT USE FOR: migrating between test frameworks (MSTest\u002FNUnit to xUnit.net), migrating from VSTest to Microsoft.Testing.Platform (use migrate-vstest-to-mtp). For xUnit v3 MTP filter syntax (--filter-class, --filter-trait, --filter-query), also load migrate-vstest-to-mtp.","weiflycc-cmd\u002Fskills","weiflycc-cmd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250846518?v=4","01M756C4PFGZJWKK04WFB9S5XF","威飛工作室","01M756C4QJJ66QDXN2RN6SXY87",0,"MIT","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-test\u002Fskills\u002Fmigrate-xunit-to-xunit-v3\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: migrate-xunit-to-xunit-v3\ndescription: >\n  Migrates .NET test projects from xUnit.net v2 to xUnit.net v3.\n  USE FOR: upgrading xunit to xunit.v3.\n  DO NOT USE FOR: migrating between test frameworks (MSTest\u002FNUnit to\n  xUnit.net), migrating from VSTest to Microsoft.Testing.Platform\n  (use migrate-vstest-to-mtp). For xUnit v3 MTP filter syntax\n  (--filter-class, --filter-trait, --filter-query), also load\n  migrate-vstest-to-mtp.\nlicense: MIT\n---\n\n# xunit.v3 Migration\n\nMigrate .NET test projects from xUnit.net v2 to xUnit.net v3. The outcome is a solution where all test projects reference `xunit.v3.*` packages, compiles cleanly, and all tests pass with the same results as before migration.\n\n## When to Use\n\n- Upgrading test projects from `xunit` (v2) packages to `xunit.v3`\n- Resolving compilation errors after updating xunit package references to v3\n\n## When Not to Use\n\n- Migrating between test frameworks (e.g., MSTest or NUnit to xUnit.net) — different effort entirely\n- Migrating from VSTest to Microsoft.Testing.Platform — use `migrate-vstest-to-mtp`\n- The projects already reference `xunit.v3` — migration is done\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Test project or solution | Yes | The .NET project or solution containing xUnit.net v2 test projects |\n\n## Workflow\n\n> **Commit strategy:** Commit after each major step so the migration is reviewable and bisectable. Separate project file changes from code changes.\n\n> **Prioritization:** Steps 1-5 are required for every migration. Steps 6-12 are conditional — only apply the ones relevant to the project's code patterns. Skip steps that don't apply.\n\n### Step 1: Identify xUnit.net projects and verify compatibility\n\nSearch for test projects referencing xUnit.net v2 packages:\n\n- `xunit`\n- `xunit.abstractions`\n- `xunit.assert`\n- `xunit.core`\n- `xunit.extensibility.core`\n- `xunit.extensibility.execution`\n- `xunit.runner.visualstudio`\n\nMake sure to check the package references in project files, MSBuild props and targets files, like `Directory.Build.props`, `Directory.Build.targets`, and `Directory.Packages.props`.\n\nVerify target framework compatibility: xUnit.net v3 requires **.NET 8+** or **.NET Framework 4.7.2+**. For test library projects, .NET Standard 2.0 is also supported. If any test projects have non-compatible target frameworks, STOP here — tell the user to upgrade the target framework first. Also verify the project uses SDK-style format.\n\n### Step 2: Update package references\n\n1. Update any `PackageReference` or `PackageVersion` items for the new package names, based on the following mapping:\n\n    - `xunit` → `xunit.v3`\n    - `xunit.abstractions` → Remove entirely\n    - `xunit.assert` → `xunit.v3.assert`\n    - `xunit.core` → `xunit.v3.core`\n    - `xunit.extensibility.core` and `xunit.extensibility.execution` → `xunit.v3.extensibility.core` (if both are referenced in a project consolidate to only a single entry as the two packages are merged)\n\n2. Update all `xunit.v3.*` packages to the latest correct version available on NuGet. Also update `xunit.runner.visualstudio` to the latest version.\n\n### Step 3: Set `OutputType` to `Exe`\n\nIn each test project (excluding test library projects), set `OutputType` to `Exe` in the project file:\n\n```xml\n\u003CPropertyGroup>\n  \u003COutputType>Exe\u003C\u002FOutputType>\n\u003C\u002FPropertyGroup>\n```\n\nDepending on the solution in hand, there might be a centralized place where this can be added. For example:\n\n- If all test projects share (or can share) a common `Directory.Build.props`, add the `\u003COutputType>Exe\u003C\u002FOutputType>` property there. Note that the OutputType should not be added to `Directory.Build.targets`.\n- If all test projects share a name pattern (e.g., `*.Tests.csproj`), add a conditional property group in `Directory.Build.props` that applies only to those projects, like `\u003COutputType Condition=\"$(MSBuildProjectName.EndsWith('.Tests'))\">Exe\u003C\u002FOutputType>`. Adjust the condition as needed to target only test projects.\n- Otherwise, add the `\u003COutputType>Exe\u003C\u002FOutputType>` property to each test project file individually.\n\n### Step 4: Configure test platform\n\nPreserve the same test platform that was used with xUnit.net v2. xUnit.net v2 always uses VSTest except if the project used `YTest.MTP.XUnit2`.\n\n- If the project had a reference to `YTest.MTP.XUnit2`:\n  - Remove the reference to `YTest.MTP.XUnit2` completely.\n  - Add `\u003CUseMicrosoftTestingPlatformRunner>true\u003C\u002FUseMicrosoftTestingPlatformRunner>` to `Directory.Build.props` under an unconditional `PropertyGroup`.\n- If the project did NOT reference `YTest.MTP.XUnit2` (the common case):\n  - Add `\u003CIsTestingPlatformApplication>false\u003C\u002FIsTestingPlatformApplication>` to `Directory.Build.props` under an unconditional `PropertyGroup`. If `Directory.Build.props` doesn't exist, create it. This keeps the project on VSTest.\n\n### Step 5: Remove `Xunit.Abstractions` usings\n\nFind any `using Xunit.Abstractions;` directives in C# files and remove them completely.\n\n### Step 6: Address `async void` breaking change (if applicable)\n\nIn xUnit.net v3, `async void` test methods are no longer supported and will fail to compile. Search for any test methods declared with `async void` and change them to `async Task`. Test methods can be identified via the `[Fact]` or `[Theory]` attributes or other test attributes.\n\n### Step 7: Address breaking change of attributes (if applicable)\n\nIn xUnit.net v3, some attributes were updated so that they accept a `System.Type` instead of two strings (fully qualified type name and assembly name). These attributes are:\n\n- `CollectionBehaviorAttribute`\n- `TestCaseOrdererAttribute`\n- `TestCollectionOrdererAttribute`\n- `TestFrameworkAttribute`\n\nFor example, `[assembly: CollectionBehavior(\"MyNamespace.MyCollectionFactory\", \"MyAssembly\")]` must be converted to `[assembly: CollectionBehavior(typeof(MyNamespace.MyCollectionFactory))]`.\n\n### Step 8: Inheriting from FactAttribute or TheoryAttribute (if applicable)\n\nIdentify if there are any custom attributes that inherit from `FactAttribute` or `TheoryAttribute`. These custom user-defined attributes must now provide source information. For example, if the attribute looked like this:\n\n```csharp\ninternal sealed class MyFactAttribute : FactAttribute\n{\n    public MyFactAttribute()\n    {\n    }\n}\n```\n\nit must be changed to this:\n\n```csharp\ninternal sealed class MyFactAttribute : FactAttribute\n{\n    public MyFactAttribute(\n        [CallerFilePath] string? sourceFilePath = null,\n        [CallerLineNumber] int sourceLineNumber = -1\n    ) : base(sourceFilePath, sourceLineNumber)\n    {\n    }\n}\n```\n\n### Step 9: Inheriting from BeforeAfterTestAttribute (if applicable)\n\nIdentify if there are any custom attributes that inherit from `BeforeAfterTestAttribute`. These custom user-defined attributes must update their method signatures. Previously, they would have `Before`\u002F`After` overrides that look like this:\n\n```csharp\n    public override void Before(MethodInfo methodUnderTest)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.Before(methodUnderTest);\n        \u002F\u002F Possibly some custom logic here\n    }\n\n    public override void After(MethodInfo methodUnderTest)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.After(methodUnderTest);\n        \u002F\u002F Possibly some custom logic here\n    }\n```\n\nit must be changed to this:\n\n```csharp\n    public override void Before(MethodInfo methodUnderTest, IXunitTest test)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.Before(methodUnderTest, test);\n        \u002F\u002F Possibly some custom logic here\n    }\n\n    public override void After(MethodInfo methodUnderTest, IXunitTest test)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.After(methodUnderTest, test);\n        \u002F\u002F Possibly some custom logic here\n    }\n```\n\n### Step 10: Address new xUnit analyzer warnings (if applicable)\n\nxunit.v3 introduced new analyzer warnings. The most notable is xUnit1051 (use `TestContext.Current.CancellationToken` for methods accepting `CancellationToken`). Address these if present.\n\n### Step 11: Migrate `Xunit.SkippableFact` (if applicable)\n\nIf there are any package references to `Xunit.SkippableFact`, remove all these package references entirely.\n\nThen, follow these steps to eliminate usages of APIs coming from the removed package reference:\n\n- Update any `SkippableFact` attribute to the regular `Fact` attribute.\n- Update any `SkippableTheory` attribute to the regular `Theory` attribute.\n- Change `Skip.If` method calls to `Assert.SkipWhen`.\n- Change `Skip.IfNot` method calls to `Assert.SkipUnless`.\n\n### Step 12: Update companion packages (if applicable)\n\n- `Xunit.Combinatorial` 1.x → latest 2.x\n- `Xunit.StaFact` 1.x → latest 3.x\n\n### Step 13: Build and verify\n\nBuild the solution and fix any remaining compilation errors. Run `dotnet test` to verify all tests pass with the same results as before migration.\n","# xunit.v3 Migration\n\nMigrate .NET test projects from xUnit.net v2 to xUnit.net v3. The outcome is a solution where all test projects reference `xunit.v3.*` packages, compiles cleanly, and all tests pass with the same results as before migration.\n\n## When to Use\n\n- Upgrading test projects from `xunit` (v2) packages to `xunit.v3`\n- Resolving compilation errors after updating xunit package references to v3\n\n## When Not to Use\n\n- Migrating between test frameworks (e.g., MSTest or NUnit to xUnit.net) — different effort entirely\n- Migrating from VSTest to Microsoft.Testing.Platform — use `migrate-vstest-to-mtp`\n- The projects already reference `xunit.v3` — migration is done\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| Test project or solution | Yes | The .NET project or solution containing xUnit.net v2 test projects |\n\n## Workflow\n\n> **Commit strategy:** Commit after each major step so the migration is reviewable and bisectable. Separate project file changes from code changes.\n\n> **Prioritization:** Steps 1-5 are required for every migration. Steps 6-12 are conditional — only apply the ones relevant to the project's code patterns. Skip steps that don't apply.\n\n### Step 1: Identify xUnit.net projects and verify compatibility\n\nSearch for test projects referencing xUnit.net v2 packages:\n\n- `xunit`\n- `xunit.abstractions`\n- `xunit.assert`\n- `xunit.core`\n- `xunit.extensibility.core`\n- `xunit.extensibility.execution`\n- `xunit.runner.visualstudio`\n\nMake sure to check the package references in project files, MSBuild props and targets files, like `Directory.Build.props`, `Directory.Build.targets`, and `Directory.Packages.props`.\n\nVerify target framework compatibility: xUnit.net v3 requires **.NET 8+** or **.NET Framework 4.7.2+**. For test library projects, .NET Standard 2.0 is also supported. If any test projects have non-compatible target frameworks, STOP here — tell the user to upgrade the target framework first. Also verify the project uses SDK-style format.\n\n### Step 2: Update package references\n\n1. Update any `PackageReference` or `PackageVersion` items for the new package names, based on the following mapping:\n\n    - `xunit` → `xunit.v3`\n    - `xunit.abstractions` → Remove entirely\n    - `xunit.assert` → `xunit.v3.assert`\n    - `xunit.core` → `xunit.v3.core`\n    - `xunit.extensibility.core` and `xunit.extensibility.execution` → `xunit.v3.extensibility.core` (if both are referenced in a project consolidate to only a single entry as the two packages are merged)\n\n2. Update all `xunit.v3.*` packages to the latest correct version available on NuGet. Also update `xunit.runner.visualstudio` to the latest version.\n\n### Step 3: Set `OutputType` to `Exe`\n\nIn each test project (excluding test library projects), set `OutputType` to `Exe` in the project file:\n\n```xml\n\u003CPropertyGroup>\n  \u003COutputType>Exe\u003C\u002FOutputType>\n\u003C\u002FPropertyGroup>\n```\n\nDepending on the solution in hand, there might be a centralized place where this can be added. For example:\n\n- If all test projects share (or can share) a common `Directory.Build.props`, add the `\u003COutputType>Exe\u003C\u002FOutputType>` property there. Note that the OutputType should not be added to `Directory.Build.targets`.\n- If all test projects share a name pattern (e.g., `*.Tests.csproj`), add a conditional property group in `Directory.Build.props` that applies only to those projects, like `\u003COutputType Condition=\"$(MSBuildProjectName.EndsWith('.Tests'))\">Exe\u003C\u002FOutputType>`. Adjust the condition as needed to target only test projects.\n- Otherwise, add the `\u003COutputType>Exe\u003C\u002FOutputType>` property to each test project file individually.\n\n### Step 4: Configure test platform\n\nPreserve the same test platform that was used with xUnit.net v2. xUnit.net v2 always uses VSTest except if the project used `YTest.MTP.XUnit2`.\n\n- If the project had a reference to `YTest.MTP.XUnit2`:\n  - Remove the reference to `YTest.MTP.XUnit2` completely.\n  - Add `\u003CUseMicrosoftTestingPlatformRunner>true\u003C\u002FUseMicrosoftTestingPlatformRunner>` to `Directory.Build.props` under an unconditional `PropertyGroup`.\n- If the project did NOT reference `YTest.MTP.XUnit2` (the common case):\n  - Add `\u003CIsTestingPlatformApplication>false\u003C\u002FIsTestingPlatformApplication>` to `Directory.Build.props` under an unconditional `PropertyGroup`. If `Directory.Build.props` doesn't exist, create it. This keeps the project on VSTest.\n\n### Step 5: Remove `Xunit.Abstractions` usings\n\nFind any `using Xunit.Abstractions;` directives in C# files and remove them completely.\n\n### Step 6: Address `async void` breaking change (if applicable)\n\nIn xUnit.net v3, `async void` test methods are no longer supported and will fail to compile. Search for any test methods declared with `async void` and change them to `async Task`. Test methods can be identified via the `[Fact]` or `[Theory]` attributes or other test attributes.\n\n### Step 7: Address breaking change of attributes (if applicable)\n\nIn xUnit.net v3, some attributes were updated so that they accept a `System.Type` instead of two strings (fully qualified type name and assembly name). These attributes are:\n\n- `CollectionBehaviorAttribute`\n- `TestCaseOrdererAttribute`\n- `TestCollectionOrdererAttribute`\n- `TestFrameworkAttribute`\n\nFor example, `[assembly: CollectionBehavior(\"MyNamespace.MyCollectionFactory\", \"MyAssembly\")]` must be converted to `[assembly: CollectionBehavior(typeof(MyNamespace.MyCollectionFactory))]`.\n\n### Step 8: Inheriting from FactAttribute or TheoryAttribute (if applicable)\n\nIdentify if there are any custom attributes that inherit from `FactAttribute` or `TheoryAttribute`. These custom user-defined attributes must now provide source information. For example, if the attribute looked like this:\n\n```csharp\ninternal sealed class MyFactAttribute : FactAttribute\n{\n    public MyFactAttribute()\n    {\n    }\n}\n```\n\nit must be changed to this:\n\n```csharp\ninternal sealed class MyFactAttribute : FactAttribute\n{\n    public MyFactAttribute(\n        [CallerFilePath] string? sourceFilePath = null,\n        [CallerLineNumber] int sourceLineNumber = -1\n    ) : base(sourceFilePath, sourceLineNumber)\n    {\n    }\n}\n```\n\n### Step 9: Inheriting from BeforeAfterTestAttribute (if applicable)\n\nIdentify if there are any custom attributes that inherit from `BeforeAfterTestAttribute`. These custom user-defined attributes must update their method signatures. Previously, they would have `Before`\u002F`After` overrides that look like this:\n\n```csharp\n    public override void Before(MethodInfo methodUnderTest)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.Before(methodUnderTest);\n        \u002F\u002F Possibly some custom logic here\n    }\n\n    public override void After(MethodInfo methodUnderTest)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.After(methodUnderTest);\n        \u002F\u002F Possibly some custom logic here\n    }\n```\n\nit must be changed to this:\n\n```csharp\n    public override void Before(MethodInfo methodUnderTest, IXunitTest test)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.Before(methodUnderTest, test);\n        \u002F\u002F Possibly some custom logic here\n    }\n\n    public override void After(MethodInfo methodUnderTest, IXunitTest test)\n    {\n        \u002F\u002F Possibly some custom logic here\n        base.After(methodUnderTest, test);\n        \u002F\u002F Possibly some custom logic here\n    }\n```\n\n### Step 10: Address new xUnit analyzer warnings (if applicable)\n\nxunit.v3 introduced new analyzer warnings. The most notable is xUnit1051 (use `TestContext.Current.CancellationToken` for methods accepting `CancellationToken`). Address these if present.\n\n### Step 11: Migrate `Xunit.SkippableFact` (if applicable)\n\nIf there are any package references to `Xunit.SkippableFact`, remove all these package references entirely.\n\nThen, follow these steps to eliminate usages of APIs coming from the removed package reference:\n\n- Update any `SkippableFact` attribute to the regular `Fact` attribute.\n- Update any `SkippableTheory` attribute to the regular `Theory` attribute.\n- Change `Skip.If` method calls to `Assert.SkipWhen`.\n- Change `Skip.IfNot` method calls to `Assert.SkipUnless`.\n\n### Step 12: Update companion packages (if applicable)\n\n- `Xunit.Combinatorial` 1.x → latest 2.x\n- `Xunit.StaFact` 1.x → latest 3.x\n\n### Step 13: Build and verify\n\nBuild the solution and fix any remaining compilation errors. Run `dotnet test` to verify all tests pass with the same results as before migration.\n",{"name":5,"license":15,"description":24},"Migrates .NET test projects from xUnit.net v2 to xUnit.net v3. USE FOR: upgrading xunit to xunit.v3. DO NOT USE FOR: migrating between test frameworks (MSTest\u002FNUnit to xUnit.net), migrating from VSTest to Microsoft.Testing.Platform (use migrate-vstest-to-mtp). For xUnit v3 MTP filter syntax (--filter-class, --filter-trait, --filter-query), also load migrate-vstest-to-mtp.\n","main","5810d492c9b301d8227f932bf87b5c954c4fa4d6","plugins\u002Fdotnet-test\u002Fskills\u002Fmigrate-xunit-to-xunit-v3","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd","weiflycc.com","2026-11-10 03:26:55",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add weiflycc-cmd\u002Fskills --skill migrate-xunit-to-xunit-v3",{"tool":38,"command":39},"bunx","bunx skills add weiflycc-cmd\u002Fskills --skill migrate-xunit-to-xunit-v3",{"tool":41,"command":42},"pnpm","pnpm dlx skills add weiflycc-cmd\u002Fskills --skill migrate-xunit-to-xunit-v3","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-test\u002Fskills\u002Fmigrate-xunit-to-xunit-v3\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M76SGT4WG5682JQJ0V3NSK6X","system-text-json-net11","Provides guidance on new System.Text.Json APIs introduced in .NET 11. It covers typed JsonTypeInfo access via GetTypeInfo\u003CT> and TryGetTypeInfo\u003CT> on JsonSerializerOptions, and the new JsonNamingPolicy.PascalCase static property. Use when serializing or deserializing JSON in .NET 11 applications and needing typed metadata access or PascalCase property naming.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fsystem-text-json-net11\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M76SGPNZYYV9BCZJW7BF7J8A","nuget-trusted-publishing","Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet\u002Flogin, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fnuget-trusted-publishing\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M76SGHVNBNVM1DMVDYTMAE5G","dotnet-pinvoke","Correctly call native (C\u002FC++) libraries from .NET using P\u002FInvoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P\u002FInvoke 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\u002Fnative boundary. DO NOT USE FOR: COM interop, C++\u002FCLI mixed-mode assemblies, or pure managed code with no native dependencies.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fdotnet-pinvoke\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M76SGDB9Z3GSB1CFW314NC84","csharp-scripts","Run file-based C# apps with the .NET CLI when the user explicitly wants C#\u002F.NET code without creating a project. Use for C# language\u002FAPI experiments, one-file C# apps, small multi-file C# apps composed with `#:include`\u002F`#:exclude`, or C# file-based apps linked with `#:ref`. Do not use for language-agnostic throwaway scripts, generic computations, Python\u002FPowerShell-style automation, full projects, or existing app integration.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fcsharp-scripts\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M76SG805T8W764WAKB1NP3CJ","thread-abort-migration","Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-upgrade\u002Fskills\u002Fthread-abort-migration\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M76SG2588ZJBE5C51HYJJSKV","migrate-nullable-references","Enable nullable reference types in a C# project and systematically resolve all warnings. USE FOR: adopting NRTs in existing codebases, file-by-file or project-wide migration, fixing CS8602\u002FCS8618\u002FCS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, upgrading dependencies with new nullable annotations. DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-upgrade\u002Fskills\u002Fmigrate-nullable-references\u002FSKILL.md",[],[]]