[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756JSWJ1J5K1Y4JNEF1NFD8":3,"skill-same:01M756JSWJ1J5K1Y4JNEF1NFD8":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M756JSWJ1J5K1Y4JNEF1NFD8","build-perf-diagnostics",null,"Diagnose MSBuild build performance bottlenecks using binary log analysis. Only activate in MSBuild\u002F.NET build context. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target\u002FTask Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, errors, search, items, properties); falls back to dotnet msbuild binlog replay + grep\u002Fcat when the MCP is unavailable.","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-msbuild\u002Fskills\u002Fbuild-perf-diagnostics\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: build-perf-diagnostics\ndescription: \"Diagnose MSBuild build performance bottlenecks using binary log analysis. Only activate in MSBuild\u002F.NET build context. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target\u002FTask Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems. INVOKES: binlog MCP server tools (overview, errors, search, items, properties); falls back to dotnet msbuild binlog replay + grep\u002Fcat when the MCP is unavailable.\"\nlicense: MIT\n---\n\n## Performance Analysis Methodology\n\n1. **Generate a binlog**: `dotnet build \u002Fbl:{} -m`\n2. Use the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) which is bundled with this plugin\n\n### Alternate flow when MCP is unavailable: binlog replay to text logs\n\n1. **Generate a binlog**: `dotnet build \u002Fbl:{} -m`\n2. **Replay to diagnostic log with performance summary**:\n   ```bash\n   dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary\n   ```\n3. **Read the performance summary** (at the end of `full.log`):\n   ```bash\n   grep \"Target Performance Summary\\|Task Performance Summary\" -A 50 full.log\n   ```\n4. **Find expensive targets and tasks**: The PerformanceSummary section lists all targets\u002Ftasks sorted by cumulative time\n5. **Check for node utilization**: grep for scheduling and node messages\n   ```bash\n   grep -i \"node.*assigned\\|building with\\|scheduler\" full.log | head -30\n   ```\n6. **Check analyzers**: grep for analyzer timing\n   ```bash\n   grep -i \"analyzer.*elapsed\\|Total analyzer execution time\\|CompilerAnalyzerDriver\" full.log\n   ```\n\n## Key Metrics and Thresholds\n\n- **Build duration**: what's \"normal\" — small project \u003C10s, medium \u003C60s, large \u003C5min\n- **Node utilization**: ideal is >80% active time across nodes. Low utilization = serialization bottleneck\n- **Single target domination**: if one target is >50% of build time, investigate\n- **Analyzer time vs compile time**: analyzers should be \u003C30% of Csc task time. If higher, consider removing expensive analyzers\n- **RAR time**: ResolveAssemblyReference >5s is concerning. >15s is pathological\n\n## Common Bottlenecks\n\n### 1. ResolveAssemblyReference (RAR) Slowness\n\n- **Symptoms**: RAR taking >5s per project\n- **Root causes**: too many assembly references, network-based reference paths, large assembly search paths\n- **Fixes**: reduce reference count, use `\u003CDesignTimeBuild>false\u003C\u002FDesignTimeBuild>` for RAR-heavy analysis, set `\u003CResolveAssemblyReferencesSilent>true\u003C\u002FResolveAssemblyReferencesSilent>` for diagnostic\n- **Advanced**: `\u003CDesignTimeBuild>` and `\u003CResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch>`\n- **Key insight**: RAR runs unconditionally even on incremental builds because users may have installed targeting packs or GACed assemblies (see dotnet\u002Fmsbuild#2015). With .NET Core micro-assemblies, the reference count is often very high.\n- **Reduce transitive references**: Set `\u003CDisableTransitiveProjectReferences>true\u003C\u002FDisableTransitiveProjectReferences>` to avoid pulling in the full transitive closure (note: projects may need to add direct references for any types they consume). Use `ReferenceOutputAssembly=\"false\"` on ProjectReferences that are only needed at build time (not API surface). Trim unused PackageReferences.\n\n### 2. Roslyn Analyzers and Source Generators\n\n- **Symptoms**: Csc task takes much longer than expected for file count (>2× clean compile time)\n- **Diagnosis**: Check the Task Performance Summary in the replayed log for Csc task time; grep for analyzer timing messages; compare Csc duration with and without analyzers (`\u002Fp:RunAnalyzers=false`)\n- **Fixes**:\n  - Conditionally disable in dev: `\u003CRunAnalyzers Condition=\"'$(ContinuousIntegrationBuild)' != 'true'\">false\u003C\u002FRunAnalyzers>`\n  - Per-configuration: `\u003CRunAnalyzers Condition=\"'$(Configuration)' == 'Debug'\">false\u003C\u002FRunAnalyzers>`\n  - Code-style only: `\u003CEnforceCodeStyleInBuild Condition=\"'$(ContinuousIntegrationBuild)' == 'true'\">true\u003C\u002FEnforceCodeStyleInBuild>`\n  - Remove genuinely redundant analyzers from inner loop\n  - Severity config in .editorconfig for less critical rules\n- **Key principle**: Preserve analyzer enforcement in CI. Never just \"remove\" analyzers — configure them conditionally.\n- **GlobalPackageReference**: Analyzers added via `GlobalPackageReference` in `Directory.Packages.props` apply to ALL projects. Consider if test projects need the same analyzer set as production code.\n- **EnforceCodeStyleInBuild**: When set to `true` in `Directory.Build.props`, forces code-style analysis on every build. Should be conditional on CI environment (`ContinuousIntegrationBuild`) to avoid slowing dev inner loop.\n\n### 3. Serialization Bottlenecks (Single-threaded targets)\n\n- **Symptoms**: Performance summary shows most build time concentrated in a single project; diagnostic log shows idle nodes while one works\n- **Common culprits**: targets without proper dependency declaration, single project on critical path\n- **Fixes**: split large projects, optimize the critical path project, ensure proper `BuildInParallel`\n\n### 4. Excessive File I\u002FO (Copy tasks)\n\n- **Symptoms**: Copy task shows high aggregate time\n- **Root causes**: copying thousands of files, copying across network drives, Copy task unintentionally running once per item (per-file) instead of as a single batch (see dotnet\u002Fmsbuild#12884)\n- **Fixes**: use hardlinks (`\u003CCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>true\u003C\u002FCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>`), reduce CopyToOutputDirectory items, use `\u003CUseCommonOutputDirectory>true\u003C\u002FUseCommonOutputDirectory>` when appropriate, set `\u003CSkipCopyUnchangedFiles>true\u003C\u002FSkipCopyUnchangedFiles>`, consider `--artifacts-path` (.NET 8+) for centralized output layout\n- **Dev Drive**: On Windows, switching to a Dev Drive (ReFS with copy-on-write and reduced Defender scans) can significantly reduce file I\u002FO overhead for Copy-heavy builds. Recommend for both dev machines and self-hosted CI agents.\n\n### 5. Evaluation Overhead\n\n- **Symptoms**: build starts slow before any compilation\n- **Root causes**: complex Directory.Build.props, wildcard globs scanning large directories, NuGetSdkResolver overhead (adds 180-400ms per project evaluation even when restored — see dotnet\u002Fmsbuild#4025)\n- **Fixes**: reduce Directory.Build.props complexity, use `\u003CEnableDefaultItems>false\u003C\u002FEnableDefaultItems>` for legacy projects with explicit file lists, avoid NuGet-based SDK resolvers if possible\n- See: `eval-performance` skill for detailed guidance\n\n### 6. NuGet Restore in Build\n\n- **Symptoms**: restore runs every build even when unnecessary\n- **Fixes**:\n  - Separate restore from build: `dotnet restore` then `dotnet build --no-restore`\n  - Enable static graph evaluation: `\u003CRestoreUseStaticGraphEvaluation>true\u003C\u002FRestoreUseStaticGraphEvaluation>` in Directory.Build.props — can save significant time in large builds (results are workload-dependent)\n\n### 7. Large Project Count and Graph Shape\n\n- **Symptoms**: many small projects, each takes minimal time but overhead adds up; deep dependency chains serialize the build\n- **Consider**: project consolidation, or use `\u002Fgraph` mode for better scheduling\n- **Graph shape matters**: a wide dependency graph (few levels, many parallel branches) builds faster than a deep one (many levels, serialized). Refactoring from deep to wide can yield significant improvements in both clean and incremental build times.\n- **Actions**: look for unnecessary project dependencies, consider splitting a bottleneck project into two, or merging small leaf projects\n\n## Using Binlog Replay for Performance Analysis\n\nStep-by-step workflow using text log replay:\n\n1. **Replay with performance summary**:\n   ```bash\n   dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary\n   ```\n2. **Read target\u002Ftask performance summaries** (at the end of `full.log`):\n   ```bash\n   grep \"Target Performance Summary\\|Task Performance Summary\" -A 50 full.log\n   ```\n   This shows all targets and tasks sorted by cumulative time — equivalent to finding expensive targets\u002Ftasks.\n3. **Find per-project build times**:\n   ```bash\n   grep \"done building project\\|Project Performance Summary\" full.log\n   ```\n4. **Check parallelism** (multi-node scheduling):\n   ```bash\n   grep -i \"node.*assigned\\|RequiresLeadingNewline\\|Building with\" full.log | head -30\n   ```\n5. **Check analyzer overhead**:\n   ```bash\n   grep -i \"Total analyzer execution time\\|analyzer.*elapsed\\|CompilerAnalyzerDriver\" full.log\n   ```\n6. **Drill into a specific slow target**:\n   ```bash\n   grep 'Target \"CoreCompile\"\\|Target \"ResolveAssemblyReferences\"' full.log\n   ```\n\n## Quick Wins Checklist\n\n- [ ] Use `\u002Fmaxcpucount` (or `-m`) for parallel builds\n- [ ] Separate restore from build (`dotnet restore` then `dotnet build --no-restore`)\n- [ ] Enable static graph restore (`\u003CRestoreUseStaticGraphEvaluation>true\u003C\u002FRestoreUseStaticGraphEvaluation>`)\n- [ ] Enable hardlinks for Copy (`\u003CCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>true\u003C\u002FCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>`)\n- [ ] Disable analyzers conditionally in dev inner loop: `\u003CRunAnalyzers Condition=\"'$(ContinuousIntegrationBuild)' != 'true'\">false\u003C\u002FRunAnalyzers>`\n- [ ] Enable reference assemblies (`\u003CProduceReferenceAssembly>true\u003C\u002FProduceReferenceAssembly>`)\n- [ ] Check for broken incremental builds (see `incremental-build` skill)\n- [ ] Check for bin\u002Fobj clashes (see `check-bin-obj-clash` skill)\n- [ ] Use graph build (`\u002Fgraph`) for multi-project solutions\n- [ ] Use `--artifacts-path` (.NET 8+) for centralized output layout\n- [ ] Enable Dev Drive (ReFS) on Windows dev machines and self-hosted CI\n\n## Impact Categorization\n\nWhen reporting findings, categorize by impact to help prioritize fixes:\n\n- 🔴 **HIGH IMPACT** (do first): Items consuming >10% of total build time, or a single target >50% of build time\n- 🟡 **MEDIUM IMPACT**: Items consuming 2-10% of build time\n- 🟢 **QUICK WINS**: Easy changes with modest impact (e.g., property flags in Directory.Build.props)\n","## Performance Analysis Methodology\n\n1. **Generate a binlog**: `dotnet build \u002Fbl:{} -m`\n2. Use the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) which is bundled with this plugin\n\n### Alternate flow when MCP is unavailable: binlog replay to text logs\n\n1. **Generate a binlog**: `dotnet build \u002Fbl:{} -m`\n2. **Replay to diagnostic log with performance summary**:\n   ```bash\n   dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary\n   ```\n3. **Read the performance summary** (at the end of `full.log`):\n   ```bash\n   grep \"Target Performance Summary\\|Task Performance Summary\" -A 50 full.log\n   ```\n4. **Find expensive targets and tasks**: The PerformanceSummary section lists all targets\u002Ftasks sorted by cumulative time\n5. **Check for node utilization**: grep for scheduling and node messages\n   ```bash\n   grep -i \"node.*assigned\\|building with\\|scheduler\" full.log | head -30\n   ```\n6. **Check analyzers**: grep for analyzer timing\n   ```bash\n   grep -i \"analyzer.*elapsed\\|Total analyzer execution time\\|CompilerAnalyzerDriver\" full.log\n   ```\n\n## Key Metrics and Thresholds\n\n- **Build duration**: what's \"normal\" — small project \u003C10s, medium \u003C60s, large \u003C5min\n- **Node utilization**: ideal is >80% active time across nodes. Low utilization = serialization bottleneck\n- **Single target domination**: if one target is >50% of build time, investigate\n- **Analyzer time vs compile time**: analyzers should be \u003C30% of Csc task time. If higher, consider removing expensive analyzers\n- **RAR time**: ResolveAssemblyReference >5s is concerning. >15s is pathological\n\n## Common Bottlenecks\n\n### 1. ResolveAssemblyReference (RAR) Slowness\n\n- **Symptoms**: RAR taking >5s per project\n- **Root causes**: too many assembly references, network-based reference paths, large assembly search paths\n- **Fixes**: reduce reference count, use `\u003CDesignTimeBuild>false\u003C\u002FDesignTimeBuild>` for RAR-heavy analysis, set `\u003CResolveAssemblyReferencesSilent>true\u003C\u002FResolveAssemblyReferencesSilent>` for diagnostic\n- **Advanced**: `\u003CDesignTimeBuild>` and `\u003CResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch>`\n- **Key insight**: RAR runs unconditionally even on incremental builds because users may have installed targeting packs or GACed assemblies (see dotnet\u002Fmsbuild#2015). With .NET Core micro-assemblies, the reference count is often very high.\n- **Reduce transitive references**: Set `\u003CDisableTransitiveProjectReferences>true\u003C\u002FDisableTransitiveProjectReferences>` to avoid pulling in the full transitive closure (note: projects may need to add direct references for any types they consume). Use `ReferenceOutputAssembly=\"false\"` on ProjectReferences that are only needed at build time (not API surface). Trim unused PackageReferences.\n\n### 2. Roslyn Analyzers and Source Generators\n\n- **Symptoms**: Csc task takes much longer than expected for file count (>2× clean compile time)\n- **Diagnosis**: Check the Task Performance Summary in the replayed log for Csc task time; grep for analyzer timing messages; compare Csc duration with and without analyzers (`\u002Fp:RunAnalyzers=false`)\n- **Fixes**:\n  - Conditionally disable in dev: `\u003CRunAnalyzers Condition=\"'$(ContinuousIntegrationBuild)' != 'true'\">false\u003C\u002FRunAnalyzers>`\n  - Per-configuration: `\u003CRunAnalyzers Condition=\"'$(Configuration)' == 'Debug'\">false\u003C\u002FRunAnalyzers>`\n  - Code-style only: `\u003CEnforceCodeStyleInBuild Condition=\"'$(ContinuousIntegrationBuild)' == 'true'\">true\u003C\u002FEnforceCodeStyleInBuild>`\n  - Remove genuinely redundant analyzers from inner loop\n  - Severity config in .editorconfig for less critical rules\n- **Key principle**: Preserve analyzer enforcement in CI. Never just \"remove\" analyzers — configure them conditionally.\n- **GlobalPackageReference**: Analyzers added via `GlobalPackageReference` in `Directory.Packages.props` apply to ALL projects. Consider if test projects need the same analyzer set as production code.\n- **EnforceCodeStyleInBuild**: When set to `true` in `Directory.Build.props`, forces code-style analysis on every build. Should be conditional on CI environment (`ContinuousIntegrationBuild`) to avoid slowing dev inner loop.\n\n### 3. Serialization Bottlenecks (Single-threaded targets)\n\n- **Symptoms**: Performance summary shows most build time concentrated in a single project; diagnostic log shows idle nodes while one works\n- **Common culprits**: targets without proper dependency declaration, single project on critical path\n- **Fixes**: split large projects, optimize the critical path project, ensure proper `BuildInParallel`\n\n### 4. Excessive File I\u002FO (Copy tasks)\n\n- **Symptoms**: Copy task shows high aggregate time\n- **Root causes**: copying thousands of files, copying across network drives, Copy task unintentionally running once per item (per-file) instead of as a single batch (see dotnet\u002Fmsbuild#12884)\n- **Fixes**: use hardlinks (`\u003CCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>true\u003C\u002FCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>`), reduce CopyToOutputDirectory items, use `\u003CUseCommonOutputDirectory>true\u003C\u002FUseCommonOutputDirectory>` when appropriate, set `\u003CSkipCopyUnchangedFiles>true\u003C\u002FSkipCopyUnchangedFiles>`, consider `--artifacts-path` (.NET 8+) for centralized output layout\n- **Dev Drive**: On Windows, switching to a Dev Drive (ReFS with copy-on-write and reduced Defender scans) can significantly reduce file I\u002FO overhead for Copy-heavy builds. Recommend for both dev machines and self-hosted CI agents.\n\n### 5. Evaluation Overhead\n\n- **Symptoms**: build starts slow before any compilation\n- **Root causes**: complex Directory.Build.props, wildcard globs scanning large directories, NuGetSdkResolver overhead (adds 180-400ms per project evaluation even when restored — see dotnet\u002Fmsbuild#4025)\n- **Fixes**: reduce Directory.Build.props complexity, use `\u003CEnableDefaultItems>false\u003C\u002FEnableDefaultItems>` for legacy projects with explicit file lists, avoid NuGet-based SDK resolvers if possible\n- See: `eval-performance` skill for detailed guidance\n\n### 6. NuGet Restore in Build\n\n- **Symptoms**: restore runs every build even when unnecessary\n- **Fixes**:\n  - Separate restore from build: `dotnet restore` then `dotnet build --no-restore`\n  - Enable static graph evaluation: `\u003CRestoreUseStaticGraphEvaluation>true\u003C\u002FRestoreUseStaticGraphEvaluation>` in Directory.Build.props — can save significant time in large builds (results are workload-dependent)\n\n### 7. Large Project Count and Graph Shape\n\n- **Symptoms**: many small projects, each takes minimal time but overhead adds up; deep dependency chains serialize the build\n- **Consider**: project consolidation, or use `\u002Fgraph` mode for better scheduling\n- **Graph shape matters**: a wide dependency graph (few levels, many parallel branches) builds faster than a deep one (many levels, serialized). Refactoring from deep to wide can yield significant improvements in both clean and incremental build times.\n- **Actions**: look for unnecessary project dependencies, consider splitting a bottleneck project into two, or merging small leaf projects\n\n## Using Binlog Replay for Performance Analysis\n\nStep-by-step workflow using text log replay:\n\n1. **Replay with performance summary**:\n   ```bash\n   dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary\n   ```\n2. **Read target\u002Ftask performance summaries** (at the end of `full.log`):\n   ```bash\n   grep \"Target Performance Summary\\|Task Performance Summary\" -A 50 full.log\n   ```\n   This shows all targets and tasks sorted by cumulative time — equivalent to finding expensive targets\u002Ftasks.\n3. **Find per-project build times**:\n   ```bash\n   grep \"done building project\\|Project Performance Summary\" full.log\n   ```\n4. **Check parallelism** (multi-node scheduling):\n   ```bash\n   grep -i \"node.*assigned\\|RequiresLeadingNewline\\|Building with\" full.log | head -30\n   ```\n5. **Check analyzer overhead**:\n   ```bash\n   grep -i \"Total analyzer execution time\\|analyzer.*elapsed\\|CompilerAnalyzerDriver\" full.log\n   ```\n6. **Drill into a specific slow target**:\n   ```bash\n   grep 'Target \"CoreCompile\"\\|Target \"ResolveAssemblyReferences\"' full.log\n   ```\n\n## Quick Wins Checklist\n\n- [ ] Use `\u002Fmaxcpucount` (or `-m`) for parallel builds\n- [ ] Separate restore from build (`dotnet restore` then `dotnet build --no-restore`)\n- [ ] Enable static graph restore (`\u003CRestoreUseStaticGraphEvaluation>true\u003C\u002FRestoreUseStaticGraphEvaluation>`)\n- [ ] Enable hardlinks for Copy (`\u003CCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>true\u003C\u002FCreateHardLinksForCopyFilesToOutputDirectoryIfPossible>`)\n- [ ] Disable analyzers conditionally in dev inner loop: `\u003CRunAnalyzers Condition=\"'$(ContinuousIntegrationBuild)' != 'true'\">false\u003C\u002FRunAnalyzers>`\n- [ ] Enable reference assemblies (`\u003CProduceReferenceAssembly>true\u003C\u002FProduceReferenceAssembly>`)\n- [ ] Check for broken incremental builds (see `incremental-build` skill)\n- [ ] Check for bin\u002Fobj clashes (see `check-bin-obj-clash` skill)\n- [ ] Use graph build (`\u002Fgraph`) for multi-project solutions\n- [ ] Use `--artifacts-path` (.NET 8+) for centralized output layout\n- [ ] Enable Dev Drive (ReFS) on Windows dev machines and self-hosted CI\n\n## Impact Categorization\n\nWhen reporting findings, categorize by impact to help prioritize fixes:\n\n- 🔴 **HIGH IMPACT** (do first): Items consuming >10% of total build time, or a single target >50% of build time\n- 🟡 **MEDIUM IMPACT**: Items consuming 2-10% of build time\n- 🟢 **QUICK WINS**: Easy changes with modest impact (e.g., property flags in Directory.Build.props)\n",{"name":5,"license":15,"description":7},"main","5810d492c9b301d8227f932bf87b5c954c4fa4d6","plugins\u002Fdotnet-msbuild\u002Fskills\u002Fbuild-perf-diagnostics","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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add weiflycc-cmd\u002Fskills --skill build-perf-diagnostics",{"tool":37,"command":38},"bunx","bunx skills add weiflycc-cmd\u002Fskills --skill build-perf-diagnostics",{"tool":40,"command":41},"pnpm","pnpm dlx skills add weiflycc-cmd\u002Fskills --skill build-perf-diagnostics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-msbuild\u002Fskills\u002Fbuild-perf-diagnostics\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[]]