[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699EGQJ9KG8W3ER80STX16Y":3,"skill-same:01M699EGQJ9KG8W3ER80STX16Y":67},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M699EGQJ9KG8W3ER80STX16Y","including-generated-files",null,"Own MSBuild generated-artifact integration. USE FOR: a target that creates or should create source, Content, None, or another physical file but the artifact is missing from compilation or output; target timing; evaluation-time glob misses; $(IntermediateOutputPath) placement; and FileWrites clean tracking. The prompt may describe the generated artifact without naming the producing task. DO NOT USE when the primary defect is general Include\u002FRemove\u002FUpdate semantics, item metadata or batching, duplicate\u002Foverlapping declarations, or a generated-item identity relationship; use item-management. Exclude Roslyn source-generator internals and non-MSBuild 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\u002Fincluding-generated-files\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"generated","files","including generated files","but","when","describe","defect","source","for","timing","time","artifact","relationship","do","clean","remove","Evaluation","update","create","identity","2026-11-10 10:12:30",false,"---\nname: including-generated-files\ndescription: \"Own MSBuild generated-artifact integration. USE FOR: a target that creates or should create source, Content, None, or another physical file but the artifact is missing from compilation or output; target timing; evaluation-time glob misses; $(IntermediateOutputPath) placement; and FileWrites clean tracking. The prompt may describe the generated artifact without naming the producing task. DO NOT USE when the primary defect is general Include\u002FRemove\u002FUpdate semantics, item metadata or batching, duplicate\u002Foverlapping declarations, or a generated-item identity relationship; use item-management. Exclude Roslyn source-generator internals and non-MSBuild systems.\"\nlicense: MIT\n---\n\n# Including Generated Files Into Your Build\n\n## Overview\n\nFiles generated during the build are generally ignored by the build process. This leads to confusing results such as:\n- Generated files not being included in the output directory\n- Generated source files not being compiled\n- Globs not capturing files created during the build\n\nThis happens because of how MSBuild's build phases work.\n\n## Quick Takeaway\n\nFor code files generated during the build - we need to add those to `Compile` and `FileWrites` item groups within the target generating the file(s):\n\n```xml\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n```\n\nThe target generating the file(s) should be hooked before CoreCompile and BeforeCompile targets - `BeforeTargets=\"CoreCompile;BeforeCompile\"`\n\n## Why Generated Files Are Ignored\n\nFor detailed explanation, see [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n### Evaluation Phase\n\nMSBuild reads your project, imports everything, creates Properties, expands globs for Items **outside of Targets**, and sets up the build process.\n\n### Execution Phase\n\nMSBuild runs Targets & Tasks with the provided Properties & Items to perform the build.\n\n**Key Takeaway:** Files generated during execution don't exist during evaluation, therefore they aren't found. This particularly affects files that are globbed by default, such as source files (`.cs`).\n\n## Solution: Manually Add Generated Files\n\nWhen files are generated during the build, manually add them into the build process. The approach depends on the type of file being generated.\n\n### Use `$(IntermediateOutputPath)` for Generated File Location\n\nAlways use `$(IntermediateOutputPath)` as the base directory for generated files. **Do not** hardcode `obj\\` or construct the intermediary path manually (e.g., `obj\\$(Configuration)\\$(TargetFramework)\\`). The intermediate output path can be redirected to a different location in some build configurations (e.g., shared output directories, CI environments). Using `$(IntermediateOutputPath)` ensures your target works correctly regardless of the actual path.\n\n### Always Add Generated Files to `FileWrites`\n\nEvery generated file should be added to the `FileWrites` item group. This ensures that MSBuild's `Clean` target properly removes your generated files. Without this, generated files will accumulate as stale artifacts across builds.\n\n```xml\n\u003CItemGroup>\n  \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n\u003C\u002FItemGroup>\n```\n\n### Basic Pattern (Non-Code Files)\n\nFor generated files that need to be copied to output (config files, data files, etc.), add them to `Content` or `None` items before `BeforeBuild`:\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedFiles\" BeforeTargets=\"BeforeBuild\">\n  \n  \u003C!-- Your logic that generates files goes here -->\n\n  \u003CItemGroup>\n    \u003CNone Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n    \n    \u003C!-- Capture all files of a certain type with a glob -->\n    \u003CNone Include=\"$(IntermediateOutputPath)generated\\*.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n\n    \u003C!-- Register generated files for proper cleanup -->\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)generated\\*.xyz\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\n### For Generated Source Files (Code That Needs Compilation)\n\nIf you're generating `.cs` files that need to be compiled, use **`BeforeTargets=\"CoreCompile;BeforeCompile\"`**. This is the correct timing for adding `Compile` items — it runs late enough that the file generation has occurred, but before the compiler runs. Using `BeforeBuild` is too early for some scenarios and may not work reliably with all SDK features.\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedSourceFiles\" BeforeTargets=\"CoreCompile;BeforeCompile\">\n  \u003CPropertyGroup>\n    \u003CGeneratedCodeDir>$(IntermediateOutputPath)Generated\\\u003C\u002FGeneratedCodeDir>\n    \u003CGeneratedFilePath>$(GeneratedCodeDir)MyGeneratedFile.cs\u003C\u002FGeneratedFilePath>\n  \u003C\u002FPropertyGroup>\n\n  \u003CMakeDir Directories=\"$(GeneratedCodeDir)\" \u002F>\n\n  \u003C!-- Your logic that generates the .cs file goes here -->\n\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\nNote: Specifying both `CoreCompile` and `BeforeCompile` ensures the target runs before whichever target comes first, providing robust ordering regardless of customizations in the build.\n\n## Target Timing\n\nChoose the `BeforeTargets` value based on the type of file being generated:\n\n- **`BeforeTargets=\"BeforeBuild\"`** — For non-code files added to `None` or `Content`. Runs early enough for copy-to-output scenarios.\n- **`BeforeTargets=\"CoreCompile;BeforeCompile\"`** — For generated source files added to `Compile`. Ensures the file is included before the compiler runs.\n- **`BeforeTargets=\"AssignTargetPaths\"`** — The \"final stop\" before `None` and `Content` items (among others) are transformed into new items. Use as a fallback if `BeforeBuild` is too early.\n\n## Globbing Behavior\n\nGlobs behave according to **when** the glob took place:\n\n| Glob Location | Files Captured |\n|---------------|----------------|\n| Outside of a target | Only files visible during Evaluation phase (before build starts) |\n| Inside of a target | Files visible when the target runs (can capture generated files if timed correctly) |\n\nThis is why the solution places the `\u003CItemGroup>` inside a `\u003CTarget>` - the glob runs during execution when the generated files exist.\n\n## Relevant Links\n\n- [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview)\n- [Evaluation Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#evaluation-phase)\n- [Execution Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#execution-phase)\n- [Common Item Types](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcommon-msbuild-project-items)\n- [How the SDK imports items by default](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fsdk\u002Fblob\u002Fmain\u002Fsrc\u002FTasks\u002FMicrosoft.NET.Build.Tasks\u002Ftargets\u002FMicrosoft.NET.Sdk.DefaultItems.props)\n- [Official docs: Handle generated files](https:\u002F\u002Flearn.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcustomize-your-build#handle-generated-files)\n","# Including Generated Files Into Your Build\n\n## Overview\n\nFiles generated during the build are generally ignored by the build process. This leads to confusing results such as:\n- Generated files not being included in the output directory\n- Generated source files not being compiled\n- Globs not capturing files created during the build\n\nThis happens because of how MSBuild's build phases work.\n\n## Quick Takeaway\n\nFor code files generated during the build - we need to add those to `Compile` and `FileWrites` item groups within the target generating the file(s):\n\n```xml\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n```\n\nThe target generating the file(s) should be hooked before CoreCompile and BeforeCompile targets - `BeforeTargets=\"CoreCompile;BeforeCompile\"`\n\n## Why Generated Files Are Ignored\n\nFor detailed explanation, see [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n### Evaluation Phase\n\nMSBuild reads your project, imports everything, creates Properties, expands globs for Items **outside of Targets**, and sets up the build process.\n\n### Execution Phase\n\nMSBuild runs Targets & Tasks with the provided Properties & Items to perform the build.\n\n**Key Takeaway:** Files generated during execution don't exist during evaluation, therefore they aren't found. This particularly affects files that are globbed by default, such as source files (`.cs`).\n\n## Solution: Manually Add Generated Files\n\nWhen files are generated during the build, manually add them into the build process. The approach depends on the type of file being generated.\n\n### Use `$(IntermediateOutputPath)` for Generated File Location\n\nAlways use `$(IntermediateOutputPath)` as the base directory for generated files. **Do not** hardcode `obj\\` or construct the intermediary path manually (e.g., `obj\\$(Configuration)\\$(TargetFramework)\\`). The intermediate output path can be redirected to a different location in some build configurations (e.g., shared output directories, CI environments). Using `$(IntermediateOutputPath)` ensures your target works correctly regardless of the actual path.\n\n### Always Add Generated Files to `FileWrites`\n\nEvery generated file should be added to the `FileWrites` item group. This ensures that MSBuild's `Clean` target properly removes your generated files. Without this, generated files will accumulate as stale artifacts across builds.\n\n```xml\n\u003CItemGroup>\n  \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n\u003C\u002FItemGroup>\n```\n\n### Basic Pattern (Non-Code Files)\n\nFor generated files that need to be copied to output (config files, data files, etc.), add them to `Content` or `None` items before `BeforeBuild`:\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedFiles\" BeforeTargets=\"BeforeBuild\">\n  \n  \u003C!-- Your logic that generates files goes here -->\n\n  \u003CItemGroup>\n    \u003CNone Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n    \n    \u003C!-- Capture all files of a certain type with a glob -->\n    \u003CNone Include=\"$(IntermediateOutputPath)generated\\*.xyz\" CopyToOutputDirectory=\"PreserveNewest\"\u002F>\n\n    \u003C!-- Register generated files for proper cleanup -->\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)my-generated-file.xyz\" \u002F>\n    \u003CFileWrites Include=\"$(IntermediateOutputPath)generated\\*.xyz\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\n### For Generated Source Files (Code That Needs Compilation)\n\nIf you're generating `.cs` files that need to be compiled, use **`BeforeTargets=\"CoreCompile;BeforeCompile\"`**. This is the correct timing for adding `Compile` items — it runs late enough that the file generation has occurred, but before the compiler runs. Using `BeforeBuild` is too early for some scenarios and may not work reliably with all SDK features.\n\n```xml\n\u003CTarget Name=\"IncludeGeneratedSourceFiles\" BeforeTargets=\"CoreCompile;BeforeCompile\">\n  \u003CPropertyGroup>\n    \u003CGeneratedCodeDir>$(IntermediateOutputPath)Generated\\\u003C\u002FGeneratedCodeDir>\n    \u003CGeneratedFilePath>$(GeneratedCodeDir)MyGeneratedFile.cs\u003C\u002FGeneratedFilePath>\n  \u003C\u002FPropertyGroup>\n\n  \u003CMakeDir Directories=\"$(GeneratedCodeDir)\" \u002F>\n\n  \u003C!-- Your logic that generates the .cs file goes here -->\n\n  \u003CItemGroup>\n    \u003CCompile Include=\"$(GeneratedFilePath)\" \u002F>\n    \u003CFileWrites Include=\"$(GeneratedFilePath)\" \u002F>\n  \u003C\u002FItemGroup>\n\u003C\u002FTarget>\n```\n\nNote: Specifying both `CoreCompile` and `BeforeCompile` ensures the target runs before whichever target comes first, providing robust ordering regardless of customizations in the build.\n\n## Target Timing\n\nChoose the `BeforeTargets` value based on the type of file being generated:\n\n- **`BeforeTargets=\"BeforeBuild\"`** — For non-code files added to `None` or `Content`. Runs early enough for copy-to-output scenarios.\n- **`BeforeTargets=\"CoreCompile;BeforeCompile\"`** — For generated source files added to `Compile`. Ensures the file is included before the compiler runs.\n- **`BeforeTargets=\"AssignTargetPaths\"`** — The \"final stop\" before `None` and `Content` items (among others) are transformed into new items. Use as a fallback if `BeforeBuild` is too early.\n\n## Globbing Behavior\n\nGlobs behave according to **when** the glob took place:\n\n| Glob Location | Files Captured |\n|---------------|----------------|\n| Outside of a target | Only files visible during Evaluation phase (before build starts) |\n| Inside of a target | Files visible when the target runs (can capture generated files if timed correctly) |\n\nThis is why the solution places the `\u003CItemGroup>` inside a `\u003CTarget>` - the glob runs during execution when the generated files exist.\n\n## Relevant Links\n\n- [How MSBuild Builds Projects](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview)\n- [Evaluation Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#evaluation-phase)\n- [Execution Phase](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview#execution-phase)\n- [Common Item Types](https:\u002F\u002Fdocs.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcommon-msbuild-project-items)\n- [How the SDK imports items by default](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fsdk\u002Fblob\u002Fmain\u002Fsrc\u002FTasks\u002FMicrosoft.NET.Build.Tasks\u002Ftargets\u002FMicrosoft.NET.Sdk.DefaultItems.props)\n- [Official docs: Handle generated files](https:\u002F\u002Flearn.microsoft.com\u002Fvisualstudio\u002Fmsbuild\u002Fcustomize-your-build#handle-generated-files)\n",{"name":5,"license":15,"description":7},"main","f8f2bfd77819bb789d4736ce7db4a567a37fcf7e",".agents\u002Fskills\u002Fincluding-generated-files",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add microsoft\u002Ftestfx --skill including-generated-files",{"tool":59,"command":60},"bunx","bunx skills add microsoft\u002Ftestfx --skill including-generated-files",{"tool":62,"command":63},"pnpm","pnpm dlx skills add microsoft\u002Ftestfx --skill including-generated-files","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fincluding-generated-files\u002FSKILL.md",true,[],[68,94,124,145,164,189],{"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":39},"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",[],[75,76,77,78,79,80,81,82,83,19,84,85,86,87,88,89,90,91,92,93],"dotnet","dotnet breaking changes","changes","green","project","default","local","errors","interface","upgrade","invoke","you","code","refactoring","merge","rename","library","live","assembly",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":39},"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",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[106,107,108,109,110,111,112,113,114,115,116,117,118,23,119,120,77,121,122,123],"test","testfx test value evidence","test value evidence","evidence","value","review","parallel","toolchain","commits","implementing","prs","only","use","apply","with","behavior","Safety","conventions",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"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",[],[131,122,132,112,133,134,115,135,87,136,88,137,138,139,140,141,142,143,118,144],"testfx parallel safety preflight","preflight","shared","asynchronous","exercise","concurrency","paths","isolation","helpers","diff","parallelization","lifecycle","tests","workers",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":39},"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",[],[152,153,154,155,156,157,27,158,159,116,19,118,160,161,77,162,163],"testfx localization validation","validation","localization","validate","translation","ids","tokens","entries","units","duplicate","targets","build",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"publishedAt":39},"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",[170],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},[172,173,153,106,174,109,175,176,177,117,178,118,179,180,181,182,183,184,185,186,187,188,137,27],"testfx acceptance validation","acceptance","msbuild","launcher","ci","execution","package","cache","artifacts","provenance","documentation","unrelated","shipping","results","protocol","unit","ci results",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":39},"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",[],[196,197,198,199,200,115,81,201,202,92,203,178,118,181,204,205,77,206,207,208],"session delivery hygiene","delivery","session","hygiene","scope","cleanup","work","pr","output","state","integration","guidance","gate"]