[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699DZSYNEW3N8JT740BYQG7":3,"skill-same:01M699DZSYNEW3N8JT740BYQG7":57},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M699DZSYNEW3N8JT740BYQG7","eval-performance",null,"Diagnose measured MSBuild evaluation costs in globs, imports and properties; not compilation, target-execution or incremental-build problems.","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\u002Feval-performance\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"performance","eval performance","eval","msbuild","diagnose","Evaluation","execution","properties","build","imports","2026-11-10 10:12:30",false,"---\nname: eval-performance\ndescription: \"Diagnose measured MSBuild evaluation costs in globs, imports and properties; not compilation, target-execution or incremental-build problems.\"\nlicense: MIT\n---\n\n# Diagnosing MSBuild Evaluation Performance\n\n## Scope and routing\n\nGuide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I\u002FO ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with \u002Fpp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems.\n\nEvaluation is the work MSBuild does *before* any target runs — reading project\nfiles, processing imports, expanding globs. This skill helps you **find and\nconfirm** evaluation bottlenecks. Measure first; recommend a change only when a\nmeasurement proves it is warranted.\n\n## Confirm the problem before changing anything\n\nEngage only when evaluation is *measurably* the bottleneck. Do NOT act when:\n\n- **The slowness is during compilation or target execution, not evaluation.**\n  That is not an evaluation problem — use `build-perf-diagnostics` instead.\n- **The complaint is \"rebuilds too much\" \u002F incremental build.** Use\n  `incremental-build` instead.\n- **You have no measurement.** If no binlog or timing summary shows evaluation\n  is slow, gather one first (see below). Do not guess from reading project files.\n- **A pattern below appears but evaluation is already fast.** Broad globs, deep\n  imports, or `EnableDefaultItems` are only worth flagging when the numbers show\n  they cost real time. A project that evaluates quickly needs no change.\n\nWhen a pattern is present but unmeasured, **report it as an observation and let\nthe user decide** — do not rewrite working configuration to match a \"best\npractice\" without evidence it costs measurable evaluation time. Prefer the\nsmallest, most targeted change; never disable SDK defaults as a first move.\n\n## MSBuild Evaluation Phases\n\nFor a comprehensive overview of MSBuild's evaluation and execution model, see [Build process overview](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n1. **Initial properties**: environment variables, global properties, reserved properties\n2. **Imports and property evaluation**: process `\u003CImport>`, evaluate `\u003CPropertyGroup>` top-to-bottom\n3. **Item definition evaluation**: `\u003CItemDefinitionGroup>` metadata defaults\n4. **Item evaluation**: `\u003CItemGroup>` with `Include`, `Remove`, `Update`, glob expansion\n5. **UsingTask evaluation**: register custom tasks\n\nKey insight: evaluation happens BEFORE any targets run. Slow evaluation = slow build start even when nothing needs compiling.\n\n## Diagnosing Evaluation Performance\n\n### Primary: binlog MCP (preferred)\n\nUse the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) to analyze evaluation performance:\n\n1. Use the evaluations tool to list all evaluations and their durations\n2. Use evaluation_global_properties to check for multiple evaluations with differing global properties\n3. Use evaluation_properties to inspect evaluated properties for a specific project+TFM\n4. Use imports tool to analyze the import chain depth and structure\n5. Use properties tool to check for expensive property function evaluations\n\n### Fallback: text-log replay and preprocessing (when MCP is unavailable)\n\n### Using binlog\n\n1. Replay the binlog: `dotnet msbuild build.binlog -noconlog -fl \"-flp:v=diag;logfile=full.log\"`\n2. Search for evaluation events: `grep -i 'Evaluation started\\|Evaluation finished' full.log`\n3. Multiple evaluations for the same project = overbuilding\n4. Look for \"Project evaluation started\u002Ffinished\" messages and their timestamps\n\n### Using \u002Fpp (preprocess)\n\n- `dotnet msbuild -pp:full.xml MyProject.csproj`\n- Shows the fully expanded project with ALL imports inlined\n- Use to understand: what's imported, import depth, total content volume\n- Large preprocessed output (>10K lines) = heavy evaluation\n\n### Using \u002Fclp:PerformanceSummary\n\n- Add to build command for timing breakdown\n- Shows evaluation time separately from target\u002Ftask execution\n\n## Expensive Glob Patterns\n\nOnly pursue these remedies once a measurement shows item evaluation is slow and\nthe globs are the cause; a custom glob that isn't walking large trees is fine.\n\n- Globs like `**\u002F*.cs` walk the entire directory tree\n- Default SDK globs are optimized, but custom globs may not be\n- Problem: globbing over `node_modules\u002F`, `.git\u002F`, `bin\u002F`, `obj\u002F` — millions of files\n- Remedy: use `\u003CDefaultItemExcludes>` to exclude large directories\n- Remedy: be specific with glob paths: `src\u002F**\u002F*.cs` instead of `**\u002F*.cs`\n- Remedy: use `\u003CEnableDefaultItems>false\u003C\u002FEnableDefaultItems>` only as a last resort (loses SDK defaults) — prefer the two options above first\n- Check: grep for Compile items in the diagnostic log → if Compile items include unexpected files, globs are too broad\n\n## Import Chain Analysis\n\n- Deep import chains (>20 levels) slow evaluation\n- Each import: file I\u002FO + parse + evaluate\n- Common causes: NuGet packages adding .props\u002F.targets, framework SDK imports, Directory.Build chains\n- Diagnosis: `\u002Fpp` output → search for `\u003C!-- Importing` comments to see import tree\n- Remedy (only if the chain is measurably costly): reduce transitive package imports where possible, consolidate imports\n\n## Multiple Evaluations\n\n- A project evaluated multiple times = wasted work\n- Common causes: referenced from multiple other projects with different global properties\n- Each unique set of global properties = separate evaluation\n- Diagnosis: `grep 'Evaluation started.*ProjectName' full.log` → if count > 1, check for differing global properties\n- Fix: normalize global properties, use graph build (`\u002Fgraph`)\n\n## TreatAsLocalProperty\n\n- Prevents property values from flowing to child projects via MSBuild task\n- Overuse: declaring many TreatAsLocalProperty entries adds evaluation overhead\n- Correct use: only when you genuinely need to override an inherited property\n\n## Property Function Cost\n\n- Property functions execute during evaluation\n- Most are cheap (string operations)\n- Expensive: `$([System.IO.File]::ReadAllText(...))` during evaluation — reads file on every evaluation\n- Expensive: network calls, heavy computation\n- Rule: property functions should be fast and side-effect-free\n\n## Optimization Checklist\n\n- [ ] Check preprocessed output size: `dotnet msbuild -pp:full.xml`\n- [ ] Verify evaluation count: should be 1 per project per TFM\n- [ ] Exclude large directories from globs\n- [ ] Avoid file I\u002FO in property functions during evaluation\n- [ ] Minimize import depth\n- [ ] Use graph build to reduce redundant evaluations\n- [ ] Check for unnecessary UsingTask declarations\n","# Diagnosing MSBuild Evaluation Performance\n\n## Scope and routing\n\nGuide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep import chains (>20 levels), preprocessed output >10K lines indicating heavy evaluation, property functions with file I\u002FO ($([System.IO.File]::ReadAllText(...))), multiple evaluations per project. Covers the 5 MSBuild evaluation phases, glob optimization via DefaultItemExcludes, import chain analysis with \u002Fpp preprocessing. DO NOT USE FOR: compilation-time slowness (use build-perf-diagnostics), incremental build issues (use incremental-build), non-MSBuild build systems.\n\nEvaluation is the work MSBuild does *before* any target runs — reading project\nfiles, processing imports, expanding globs. This skill helps you **find and\nconfirm** evaluation bottlenecks. Measure first; recommend a change only when a\nmeasurement proves it is warranted.\n\n## Confirm the problem before changing anything\n\nEngage only when evaluation is *measurably* the bottleneck. Do NOT act when:\n\n- **The slowness is during compilation or target execution, not evaluation.**\n  That is not an evaluation problem — use `build-perf-diagnostics` instead.\n- **The complaint is \"rebuilds too much\" \u002F incremental build.** Use\n  `incremental-build` instead.\n- **You have no measurement.** If no binlog or timing summary shows evaluation\n  is slow, gather one first (see below). Do not guess from reading project files.\n- **A pattern below appears but evaluation is already fast.** Broad globs, deep\n  imports, or `EnableDefaultItems` are only worth flagging when the numbers show\n  they cost real time. A project that evaluates quickly needs no change.\n\nWhen a pattern is present but unmeasured, **report it as an observation and let\nthe user decide** — do not rewrite working configuration to match a \"best\npractice\" without evidence it costs measurable evaluation time. Prefer the\nsmallest, most targeted change; never disable SDK defaults as a first move.\n\n## MSBuild Evaluation Phases\n\nFor a comprehensive overview of MSBuild's evaluation and execution model, see [Build process overview](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n1. **Initial properties**: environment variables, global properties, reserved properties\n2. **Imports and property evaluation**: process `\u003CImport>`, evaluate `\u003CPropertyGroup>` top-to-bottom\n3. **Item definition evaluation**: `\u003CItemDefinitionGroup>` metadata defaults\n4. **Item evaluation**: `\u003CItemGroup>` with `Include`, `Remove`, `Update`, glob expansion\n5. **UsingTask evaluation**: register custom tasks\n\nKey insight: evaluation happens BEFORE any targets run. Slow evaluation = slow build start even when nothing needs compiling.\n\n## Diagnosing Evaluation Performance\n\n### Primary: binlog MCP (preferred)\n\nUse the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) to analyze evaluation performance:\n\n1. Use the evaluations tool to list all evaluations and their durations\n2. Use evaluation_global_properties to check for multiple evaluations with differing global properties\n3. Use evaluation_properties to inspect evaluated properties for a specific project+TFM\n4. Use imports tool to analyze the import chain depth and structure\n5. Use properties tool to check for expensive property function evaluations\n\n### Fallback: text-log replay and preprocessing (when MCP is unavailable)\n\n### Using binlog\n\n1. Replay the binlog: `dotnet msbuild build.binlog -noconlog -fl \"-flp:v=diag;logfile=full.log\"`\n2. Search for evaluation events: `grep -i 'Evaluation started\\|Evaluation finished' full.log`\n3. Multiple evaluations for the same project = overbuilding\n4. Look for \"Project evaluation started\u002Ffinished\" messages and their timestamps\n\n### Using \u002Fpp (preprocess)\n\n- `dotnet msbuild -pp:full.xml MyProject.csproj`\n- Shows the fully expanded project with ALL imports inlined\n- Use to understand: what's imported, import depth, total content volume\n- Large preprocessed output (>10K lines) = heavy evaluation\n\n### Using \u002Fclp:PerformanceSummary\n\n- Add to build command for timing breakdown\n- Shows evaluation time separately from target\u002Ftask execution\n\n## Expensive Glob Patterns\n\nOnly pursue these remedies once a measurement shows item evaluation is slow and\nthe globs are the cause; a custom glob that isn't walking large trees is fine.\n\n- Globs like `**\u002F*.cs` walk the entire directory tree\n- Default SDK globs are optimized, but custom globs may not be\n- Problem: globbing over `node_modules\u002F`, `.git\u002F`, `bin\u002F`, `obj\u002F` — millions of files\n- Remedy: use `\u003CDefaultItemExcludes>` to exclude large directories\n- Remedy: be specific with glob paths: `src\u002F**\u002F*.cs` instead of `**\u002F*.cs`\n- Remedy: use `\u003CEnableDefaultItems>false\u003C\u002FEnableDefaultItems>` only as a last resort (loses SDK defaults) — prefer the two options above first\n- Check: grep for Compile items in the diagnostic log → if Compile items include unexpected files, globs are too broad\n\n## Import Chain Analysis\n\n- Deep import chains (>20 levels) slow evaluation\n- Each import: file I\u002FO + parse + evaluate\n- Common causes: NuGet packages adding .props\u002F.targets, framework SDK imports, Directory.Build chains\n- Diagnosis: `\u002Fpp` output → search for `\u003C!-- Importing` comments to see import tree\n- Remedy (only if the chain is measurably costly): reduce transitive package imports where possible, consolidate imports\n\n## Multiple Evaluations\n\n- A project evaluated multiple times = wasted work\n- Common causes: referenced from multiple other projects with different global properties\n- Each unique set of global properties = separate evaluation\n- Diagnosis: `grep 'Evaluation started.*ProjectName' full.log` → if count > 1, check for differing global properties\n- Fix: normalize global properties, use graph build (`\u002Fgraph`)\n\n## TreatAsLocalProperty\n\n- Prevents property values from flowing to child projects via MSBuild task\n- Overuse: declaring many TreatAsLocalProperty entries adds evaluation overhead\n- Correct use: only when you genuinely need to override an inherited property\n\n## Property Function Cost\n\n- Property functions execute during evaluation\n- Most are cheap (string operations)\n- Expensive: `$([System.IO.File]::ReadAllText(...))` during evaluation — reads file on every evaluation\n- Expensive: network calls, heavy computation\n- Rule: property functions should be fast and side-effect-free\n\n## Optimization Checklist\n\n- [ ] Check preprocessed output size: `dotnet msbuild -pp:full.xml`\n- [ ] Verify evaluation count: should be 1 per project per TFM\n- [ ] Exclude large directories from globs\n- [ ] Avoid file I\u002FO in property functions during evaluation\n- [ ] Minimize import depth\n- [ ] Use graph build to reduce redundant evaluations\n- [ ] Check for unnecessary UsingTask declarations\n",{"name":5,"license":15,"description":7},"main","f8f2bfd77819bb789d4736ce7db4a567a37fcf7e",".agents\u002Fskills\u002Feval-performance",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add microsoft\u002Ftestfx --skill eval-performance",{"tool":49,"command":50},"bunx","bunx skills add microsoft\u002Ftestfx --skill eval-performance",{"tool":52,"command":53},"pnpm","pnpm dlx skills add microsoft\u002Ftestfx --skill eval-performance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feval-performance\u002FSKILL.md",true,[],[58,85,116,137,156,179],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":29},"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",[],[65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84],"dotnet","dotnet breaking changes","changes","green","project","default","local","errors","interface","generated","upgrade","invoke","you","code","refactoring","merge","rename","library","live","assembly",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":96,"publishedAt":29},"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",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,67,113,114,115],"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":29},"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",[],[123,114,124,103,125,126,106,127,78,128,79,129,130,131,132,133,134,135,109,136],"testfx parallel safety preflight","preflight","shared","asynchronous","exercise","concurrency","paths","isolation","helpers","diff","parallelization","lifecycle","tests","workers",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":29},"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",[],[144,145,146,147,148,149,150,151,152,107,74,109,153,154,67,155,27],"testfx localization validation","validation","localization","validate","translation","ids","for","tokens","entries","units","duplicate","targets",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":29},"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",[162],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[164,165,145,97,22,100,166,167,25,108,168,109,169,170,171,172,173,174,175,176,177,178,129,150],"testfx acceptance validation","acceptance","launcher","ci","package","cache","artifacts","provenance","documentation","unrelated","shipping","results","protocol","unit","ci results",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":29},"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",[],[186,187,188,189,190,106,71,191,192,83,193,168,109,171,194,195,67,196,197,198],"session delivery hygiene","delivery","session","hygiene","scope","cleanup","work","pr","output","state","integration","guidance","gate"]