[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699FV3RSHA8EX5SY9Q1WEDV":3,"skill-same:01M699FV3RSHA8EX5SY9Q1WEDV":70},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M699FV3RSHA8EX5SY9Q1WEDV","target-authoring",null,"Canonical patterns for writing custom MSBuild targets. USE FOR: diagnosing and fixing custom target authoring anti-patterns; broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets); targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn); query targets returning stale results from Outputs vs Returns misuse; missing Inputs\u002FOutputs causing unnecessary rebuilds; missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, and the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.","microsoft\u002Ftestfx","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699C71CJ91B5WZ3AXG3GG2M",1059,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftarget-authoring\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"target authoring","authoring","registration","for","canonical","antipatterns","chain","across","pattern","three","query","patterns","do","writing","files","anti-patterns","broken","returns","tuning","msbuild","incremental build","sdk","directory","2026-11-10 10:12:30",false,"---\nname: target-authoring\ndescription: \"Canonical patterns for writing custom MSBuild targets. USE FOR: diagnosing and fixing custom target authoring anti-patterns; broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets); targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn); query targets returning stale results from Outputs vs Returns misuse; missing Inputs\u002FOutputs causing unnecessary rebuilds; missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, and the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.\"\nlicense: MIT\n---\n\n# Custom Target Authoring Patterns\n\nCanonical patterns from `Microsoft.Common.CurrentVersion.targets` in the MSBuild repository.\n\n## The Three-Level Target Chain\n\nEvery major entry point (Build, Rebuild, Clean) delegates to a **property** listing its dependencies, which chains through Before → Core → After:\n\n```xml\n\u003CPropertyGroup>\n  \u003CBuildDependsOn>\n    BeforeBuild;\n    CoreBuild;\n    AfterBuild\n  \u003C\u002FBuildDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003CTarget Name=\"Build\"\n    Condition=\" '$(_InvalidConfigurationWarning)' != 'true' \"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- Empty extensibility targets — users override these -->\n\u003CTarget Name=\"BeforeBuild\" \u002F>\n\u003CTarget Name=\"AfterBuild\" \u002F>\n```\n\n`CoreBuild` delegates to `$(CoreBuildDependsOn)` and includes error handlers:\n\n```xml\n\u003CTarget Name=\"CoreBuild\" DependsOnTargets=\"$(CoreBuildDependsOn)\">\n  \u003COnError ExecuteTargets=\"_TimeStampAfterCompile;PostBuildEvent\"\n      Condition=\"'$(RunPostBuildEvent)' == 'Always'\" \u002F>\n  \u003COnError ExecuteTargets=\"_CleanRecordFileWrites\" \u002F>\n\u003C\u002FTarget>\n```\n\n### Rules\n\n- Delegate to a property (`DependsOnTargets=\"$(MyTargetDependsOn)\"`), not hardcoded targets.\n- `OnError` goes inside the orchestrating target to ensure cleanup runs even on failure.\n- Empty Before\u002FAfter targets are extensibility points. Users override them; SDKs never put logic in them.\n\n## Chain Extension — Append, Never Overwrite\n\nWhen adding a custom target to an existing chain, **append** to the `DependsOn` property:\n\n```xml\n\u003C!-- GOOD: Append to existing chain -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>$(CompileDependsOn);MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- BAD: Overwrites the entire chain, dropping SDK targets -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n```\n\n## DependsOnTargets vs BeforeTargets vs AfterTargets\n\n| Mechanism | Defined in | Best for |\n|---|---|---|\n| `DependsOnTargets` | The target that needs deps | Target explicitly requires others |\n| `BeforeTargets` | The injecting target | Insert before a target you don't own |\n| `AfterTargets` | The injecting target | Insert after a target you don't own |\n\nValidation targets use `BeforeTargets` to intercept all entry points:\n\n```xml\n\u003CTarget Name=\"_CheckForInvalidConfigurationAndPlatform\"\n    BeforeTargets=\"$(BuildDependsOn);Build;$(RebuildDependsOn);Rebuild;$(CleanDependsOn);Clean\">\n\u003C\u002FTarget>\n```\n\n**Rules:**\n\n- Use `DependsOnTargets` when your target needs specific prerequisites.\n- Use `BeforeTargets`\u002F`AfterTargets` when injecting into a pipeline you don't own.\n- Prefer `BeforeTargets=\"CoreCompile\"` over modifying `$(CompileDependsOn)` when you don't control the targets file.\n\n## Returns vs Outputs\n\n```xml\n\u003C!-- Build returns items for consumption by referencing projects -->\n\u003CTarget Name=\"Build\"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- GetTargetPath is a lightweight query target -->\n\u003CTarget Name=\"GetTargetPath\" Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n```\n\n- **`Returns`** specifies what the MSBuild task receives when calling this project. Use for inter-project communication.\n- **`Outputs`** on inner targets is for incrementality (timestamp checks). Use for up-to-date detection.\n- Never mix the two purposes. Query targets (`GetTargetPath`, `GetTargetFrameworks`) should use `Returns`, not `Outputs`.\n\n## Target Naming Conventions\n\n| Pattern | Meaning | Example |\n|---|---|---|\n| `_PrefixedName` | Internal\u002Fprivate target | `_TimeStampBeforeCompile` |\n| `CoreXxx` | The actual implementation | `CoreBuild`, `CoreCompile` |\n| `BeforeXxx` \u002F `AfterXxx` | Empty extensibility hooks | `BeforeBuild`, `AfterCompile` |\n| `PrepareXxx` | Setup\u002Fvalidation phase | `PrepareForBuild` |\n| `ResolveXxx` | Discovery\u002Fresolution phase | `ResolveReferences` |\n| `GetXxx` | Lightweight query (no side effects) | `GetTargetPath` |\n\n## Complete Custom Target Template\n\n```xml\n\u003C!-- 1. Define the DependsOn chain for extensibility -->\n\u003CPropertyGroup>\n  \u003CMyFeatureDependsOn>\n    _ValidateMyFeatureInputs;\n    BeforeMyFeature;\n    CoreMyFeature;\n    AfterMyFeature\n  \u003C\u002FMyFeatureDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- 2. Outer target with Returns for inter-project communication -->\n\u003CTarget Name=\"MyFeature\"\n    DependsOnTargets=\"$(MyFeatureDependsOn)\"\n    Returns=\"@(MyFeatureOutput)\" \u002F>\n\n\u003C!-- 3. Empty extensibility points -->\n\u003CTarget Name=\"BeforeMyFeature\" \u002F>\n\u003CTarget Name=\"AfterMyFeature\" \u002F>\n\n\u003C!-- 4. Core implementation with Inputs\u002FOutputs for incrementality -->\n\u003CTarget Name=\"CoreMyFeature\"\n    Inputs=\"$(MSBuildAllProjects);@(MyFeatureInput)\"\n    Outputs=\"$(IntermediateOutputPath)myfeature.generated.cs\">\n  \u003CExec Command=\"my-tool.exe -o $(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C!-- 5. Register outputs for clean tracking -->\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n\n\u003C!-- 6. Validation target runs first in the dependency chain -->\n\u003CTarget Name=\"_ValidateMyFeatureInputs\">\n  \u003CError Text=\"MyFeatureInput items are required.\"\n         Condition=\"'@(MyFeatureInput)' == ''\" \u002F>\n\u003C\u002FTarget>\n```\n\n## Common Pitfalls\n\n- **Overwriting `DependsOn` properties** drops SDK targets silently. Always include `$(ExistingProperty)` when appending.\n- **Using `Outputs` on query targets** causes MSBuild to skip them when \"up to date,\" returning stale data. Use `Returns`.\n- **Defining targets in `.props`** means `BeforeTargets` on SDK targets have nothing to hook into yet. Move targets to `.targets`.\n- **Forgetting `OnError`** in orchestrating targets means file tracking fails on build errors, breaking subsequent incremental builds.\n","# Custom Target Authoring Patterns\n\nCanonical patterns from `Microsoft.Common.CurrentVersion.targets` in the MSBuild repository.\n\n## The Three-Level Target Chain\n\nEvery major entry point (Build, Rebuild, Clean) delegates to a **property** listing its dependencies, which chains through Before → Core → After:\n\n```xml\n\u003CPropertyGroup>\n  \u003CBuildDependsOn>\n    BeforeBuild;\n    CoreBuild;\n    AfterBuild\n  \u003C\u002FBuildDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003CTarget Name=\"Build\"\n    Condition=\" '$(_InvalidConfigurationWarning)' != 'true' \"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- Empty extensibility targets — users override these -->\n\u003CTarget Name=\"BeforeBuild\" \u002F>\n\u003CTarget Name=\"AfterBuild\" \u002F>\n```\n\n`CoreBuild` delegates to `$(CoreBuildDependsOn)` and includes error handlers:\n\n```xml\n\u003CTarget Name=\"CoreBuild\" DependsOnTargets=\"$(CoreBuildDependsOn)\">\n  \u003COnError ExecuteTargets=\"_TimeStampAfterCompile;PostBuildEvent\"\n      Condition=\"'$(RunPostBuildEvent)' == 'Always'\" \u002F>\n  \u003COnError ExecuteTargets=\"_CleanRecordFileWrites\" \u002F>\n\u003C\u002FTarget>\n```\n\n### Rules\n\n- Delegate to a property (`DependsOnTargets=\"$(MyTargetDependsOn)\"`), not hardcoded targets.\n- `OnError` goes inside the orchestrating target to ensure cleanup runs even on failure.\n- Empty Before\u002FAfter targets are extensibility points. Users override them; SDKs never put logic in them.\n\n## Chain Extension — Append, Never Overwrite\n\nWhen adding a custom target to an existing chain, **append** to the `DependsOn` property:\n\n```xml\n\u003C!-- GOOD: Append to existing chain -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>$(CompileDependsOn);MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- BAD: Overwrites the entire chain, dropping SDK targets -->\n\u003CPropertyGroup>\n  \u003CCompileDependsOn>MyCodeGenTarget\u003C\u002FCompileDependsOn>\n\u003C\u002FPropertyGroup>\n```\n\n## DependsOnTargets vs BeforeTargets vs AfterTargets\n\n| Mechanism | Defined in | Best for |\n|---|---|---|\n| `DependsOnTargets` | The target that needs deps | Target explicitly requires others |\n| `BeforeTargets` | The injecting target | Insert before a target you don't own |\n| `AfterTargets` | The injecting target | Insert after a target you don't own |\n\nValidation targets use `BeforeTargets` to intercept all entry points:\n\n```xml\n\u003CTarget Name=\"_CheckForInvalidConfigurationAndPlatform\"\n    BeforeTargets=\"$(BuildDependsOn);Build;$(RebuildDependsOn);Rebuild;$(CleanDependsOn);Clean\">\n\u003C\u002FTarget>\n```\n\n**Rules:**\n\n- Use `DependsOnTargets` when your target needs specific prerequisites.\n- Use `BeforeTargets`\u002F`AfterTargets` when injecting into a pipeline you don't own.\n- Prefer `BeforeTargets=\"CoreCompile\"` over modifying `$(CompileDependsOn)` when you don't control the targets file.\n\n## Returns vs Outputs\n\n```xml\n\u003C!-- Build returns items for consumption by referencing projects -->\n\u003CTarget Name=\"Build\"\n    DependsOnTargets=\"$(BuildDependsOn)\"\n    Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n\n\u003C!-- GetTargetPath is a lightweight query target -->\n\u003CTarget Name=\"GetTargetPath\" Returns=\"@(TargetPathWithTargetPlatformMoniker)\" \u002F>\n```\n\n- **`Returns`** specifies what the MSBuild task receives when calling this project. Use for inter-project communication.\n- **`Outputs`** on inner targets is for incrementality (timestamp checks). Use for up-to-date detection.\n- Never mix the two purposes. Query targets (`GetTargetPath`, `GetTargetFrameworks`) should use `Returns`, not `Outputs`.\n\n## Target Naming Conventions\n\n| Pattern | Meaning | Example |\n|---|---|---|\n| `_PrefixedName` | Internal\u002Fprivate target | `_TimeStampBeforeCompile` |\n| `CoreXxx` | The actual implementation | `CoreBuild`, `CoreCompile` |\n| `BeforeXxx` \u002F `AfterXxx` | Empty extensibility hooks | `BeforeBuild`, `AfterCompile` |\n| `PrepareXxx` | Setup\u002Fvalidation phase | `PrepareForBuild` |\n| `ResolveXxx` | Discovery\u002Fresolution phase | `ResolveReferences` |\n| `GetXxx` | Lightweight query (no side effects) | `GetTargetPath` |\n\n## Complete Custom Target Template\n\n```xml\n\u003C!-- 1. Define the DependsOn chain for extensibility -->\n\u003CPropertyGroup>\n  \u003CMyFeatureDependsOn>\n    _ValidateMyFeatureInputs;\n    BeforeMyFeature;\n    CoreMyFeature;\n    AfterMyFeature\n  \u003C\u002FMyFeatureDependsOn>\n\u003C\u002FPropertyGroup>\n\n\u003C!-- 2. Outer target with Returns for inter-project communication -->\n\u003CTarget Name=\"MyFeature\"\n    DependsOnTargets=\"$(MyFeatureDependsOn)\"\n    Returns=\"@(MyFeatureOutput)\" \u002F>\n\n\u003C!-- 3. Empty extensibility points -->\n\u003CTarget Name=\"BeforeMyFeature\" \u002F>\n\u003CTarget Name=\"AfterMyFeature\" \u002F>\n\n\u003C!-- 4. Core implementation with Inputs\u002FOutputs for incrementality -->\n\u003CTarget Name=\"CoreMyFeature\"\n    Inputs=\"$(MSBuildAllProjects);@(MyFeatureInput)\"\n    Outputs=\"$(IntermediateOutputPath)myfeature.generated.cs\">\n  \u003CExec Command=\"my-tool.exe -o $(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C!-- 5. Register outputs for clean tracking -->\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)myfeature.generated.cs\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n\n\u003C!-- 6. Validation target runs first in the dependency chain -->\n\u003CTarget Name=\"_ValidateMyFeatureInputs\">\n  \u003CError Text=\"MyFeatureInput items are required.\"\n         Condition=\"'@(MyFeatureInput)' == ''\" \u002F>\n\u003C\u002FTarget>\n```\n\n## Common Pitfalls\n\n- **Overwriting `DependsOn` properties** drops SDK targets silently. Always include `$(ExistingProperty)` when appending.\n- **Using `Outputs` on query targets** causes MSBuild to skip them when \"up to date,\" returning stale data. Use `Returns`.\n- **Defining targets in `.props`** means `BeforeTargets` on SDK targets have nothing to hook into yet. Move targets to `.targets`.\n- **Forgetting `OnError`** in orchestrating targets means file tracking fails on build errors, breaking subsequent incremental builds.\n",{"name":5,"license":15,"description":7},"main","f8f2bfd77819bb789d4736ce7db4a567a37fcf7e",".agents\u002Fskills\u002Ftarget-authoring",315,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 14:01:43",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add microsoft\u002Ftestfx --skill target-authoring",{"tool":62,"command":63},"bunx","bunx skills add microsoft\u002Ftestfx --skill target-authoring",{"tool":65,"command":66},"pnpm","pnpm dlx skills add microsoft\u002Ftestfx --skill target-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftarget-authoring\u002FSKILL.md",true,[],[71,98,129,150,169,193],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":42},"01M70GYY0AV0JGMTHE2CN6TNYK","dotnet-breaking-changes","Use before changing .NET\u002FC# code whose callers you do not control: a NuGet library, or a repo with PublicAPI.Shipped\u002FUnshipped.txt, ApiCompat, multiple TargetFrameworks, InternalsVisibleTo, or generated (.g.cs) partials. Green builds miss silent breaks from optional parameters, parameter names, sealing, const values, nullability, and #if. USE FOR: \"without breaking existing callers\"; adding a public method, overload, optional parameter, or interface member to a shipped library; renaming a public method or an internal helper a friend assembly uses; consolidating duplicated logic; changing a signature, nullability, default, or attribute; adding a target framework; RS0016\u002FRS0017 or ApiCompat errors; \"is this PR breaking?\". For a rename, extract, or merge, also invoke csharp-refactoring. DO NOT USE FOR: an executable whose callers all live in one project; renaming a local variable or private member, even in a shipped library; formatting; framework\u002FSDK\u002FNuGet upgrades (use dotnet-upgrade).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdotnet-breaking-changes\u002FSKILL.md",[],[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"dotnet","dotnet breaking changes","changes","green","project","default","local","errors","interface","generated","upgrade","invoke","you","code","refactoring","merge","rename","library","live","assembly",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":109,"publishedAt":42},"01M699HHE9DTZWAMPB1ZR7ZKSW","testfx-test-value-evidence","Apply the vendored test-value-evidence skill with TestFx toolchain, assertion, parallel-safety, packed-consumer, and review conventions. Use when implementing or reviewing behavior-changing TestFx PRs or commits, including source-only changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-test-value-evidence\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,80,126,127,128],"test","testfx test value evidence","test value evidence","evidence","value","review","parallel","toolchain","commits","implementing","prs","only","use","when","apply","with","behavior","Safety","conventions",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":42},"01M699HEYWH1B9XGNBFY8J2FZS","testfx-parallel-safety-preflight","Check concurrency and isolation before implementing or refactoring TestFx tests, lifecycle code, helpers, shared-state declarations, or production paths those tests exercise. Use before narrowing DoNotParallelize or ResourceLock, changing parallelization settings, or introducing asynchronous workers; repeat against the final diff.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-parallel-safety-preflight\u002FSKILL.md",[],[136,127,137,116,138,139,119,140,91,141,92,142,143,144,145,146,147,148,122,149],"testfx parallel safety preflight","preflight","shared","asynchronous","exercise","concurrency","paths","isolation","helpers","diff","parallelization","lifecycle","tests","workers",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":42},"01M699HC61ZV9GJ2C8JV03951G","testfx-localization-validation","Validate generated TestFx localization catalogs, resource IDs, placeholders and locked tokens. Use for RESX\u002FXLF changes, OneLoc PRs, localization build failures, duplicate targets or units, and orphaned translation entries.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-localization-validation\u002FSKILL.md",[],[157,158,159,160,161,162,22,163,164,120,87,122,165,166,80,167,168],"testfx localization validation","validation","localization","validate","translation","ids","tokens","entries","units","duplicate","targets","build",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":42},"01M699H9J2NWQXE4BDT6R0FH7S","testfx-acceptance-validation","Validate TestFx shipping paths and capable CI execution using packed consumers, package\u002Fcache provenance, exact exits and artifacts, and selected-versus-executed test evidence. Use for acceptance regressions, package\u002FMSBuild\u002Flauncher\u002Fprotocol changes, or skipped-only CI results; not for unrelated unit-only or documentation changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-acceptance-validation\u002FSKILL.md",[175],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[177,178,158,110,38,113,179,180,181,121,182,122,183,184,185,186,187,188,189,190,191,192,142,22],"testfx acceptance validation","acceptance","launcher","ci","execution","package","cache","artifacts","provenance","documentation","unrelated","shipping","results","protocol","unit","ci results",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":42},"01M699H70BB999BT4F627T1PHE","session-delivery-hygiene","Gate local-session scope, persistent delivery, live PR state, integration provenance, and owned cleanup. Use before implementing guidance changes, changing or pushing PR work, diagnosing package\u002Foutput mismatches, or handing off implementation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsession-delivery-hygiene\u002FSKILL.md",[],[200,201,202,203,204,119,84,205,206,96,207,182,122,185,208,209,80,210,211,212],"session delivery hygiene","delivery","session","hygiene","scope","cleanup","work","pr","output","state","integration","guidance","gate"]