[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-dotnet-build-parallelism":3,"mdc--vz9tzj-key":34,"related-repo-dotnet-build-parallelism":680,"related-org-dotnet-build-parallelism":787},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":29,"sourceUrl":32,"mdContent":33},"build-parallelism","optimize MSBuild build parallelism","Diagnose and fix under-parallelized MSBuild builds. USE WHEN a multi-project solution build is slower than expected, doesn't speed up when you add cores, pegs a single core while others idle, or you want to know why `-m` isn't helping. Note: `\u002Fmaxcpucount` default is 1 (sequential) — always pass `-m` for parallel builds. Covers finding the critical path (longest serial ProjectReference chain), graph build (`\u002Fgraph`), BuildInParallel, and solution filters (`.slnf`). DO NOT USE FOR: single-project builds, incremental issues (use incremental-build), compilation slowness inside one project (use build-perf-diagnostics), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"dotnet",".NET (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fdotnet.png",[12,16,19],{"name":13,"slug":14,"type":15},"Performance","performance","tag",{"name":17,"slug":18,"type":15},".NET","net",{"name":20,"slug":21,"type":15},"Engineering","engineering",4576,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills","2026-07-19T05:38:18.364937","MIT",332,[28],"agent-skills",{"repoUrl":23,"stars":22,"forks":26,"topics":30,"description":31},[28],"Repository for skills to assist AI coding agents with .NET and C#","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills\u002Ftree\u002FHEAD\u002Fplugins\u002Fdotnet-msbuild\u002Fskills\u002Fbuild-parallelism","---\nname: build-parallelism\ndescription: \"Diagnose and fix under-parallelized MSBuild builds. USE WHEN a multi-project solution build is slower than expected, doesn't speed up when you add cores, pegs a single core while others idle, or you want to know why `-m` isn't helping. Note: `\u002Fmaxcpucount` default is 1 (sequential) — always pass `-m` for parallel builds. Covers finding the critical path (longest serial ProjectReference chain), graph build (`\u002Fgraph`), BuildInParallel, and solution filters (`.slnf`). DO NOT USE FOR: single-project builds, incremental issues (use incremental-build), compilation slowness inside one project (use build-perf-diagnostics), non-MSBuild build systems.\"\nlicense: MIT\n---\n\n## Diagnose a slow parallel build (start here)\n\nWork this checklist in order — it targets the usual root cause (a serial\ndependency chain that no number of cores can parallelize):\n\n1. **Confirm parallelism is even on.** Rebuild with `dotnet build -m \u002Fbl:{}`\n   (PowerShell: `dotnet build -m -bl:{{}}`). `-m` with no number uses all logical\n   processors; without `-m` MSBuild runs a single node (sequential).\n2. **Find the critical path.** From the binlog, read per-project timings and the\n   node timeline. If total build time ≈ the sum of the projects on one\n   dependency chain, that chain — not CPU count — is the bottleneck.\n3. **Name the chain explicitly**, e.g. `Core → Api → Web → Tests`. A long serial\n   chain stays serial no matter how large `-m` is, because each project waits on\n   its predecessor.\n4. **Look for unnecessary `ProjectReference` edges** that lengthen the chain — a\n   reference that only needs build order (not the output assembly), or one that\n   could be a `PackageReference`, forces serialization it doesn't need.\n5. **Recommend flattening**: break false dependencies so independent projects\n   build concurrently, and consider `\u002Fgraph` for better scheduling.\n\n## MSBuild Parallelism Model\n\n- `\u002Fmaxcpucount` (or `-m`): number of worker nodes (processes)\n- Default: 1 node (sequential!). Always use `-m` for parallel builds\n- Recommended: `-m` without a number = use all logical processors\n- Each node builds one project at a time\n- Projects are scheduled based on dependency graph\n\n## Project Dependency Graph\n\n- MSBuild builds projects in dependency order (topological sort)\n- Critical path: longest chain of dependent projects determines minimum build time\n- Bottleneck: if project A depends on B, C, D and B takes 60s while C and D take 5s, B is the bottleneck\n- Diagnosis: replay binlog to diagnostic log with `performancesummary` and check Project Performance Summary — shows per-project time; grep for `node.*assigned` to check scheduling\n- Wide graphs (many independent projects) parallelize well; deep graphs (long chains) don't\n\n## Graph Build Mode (`\u002Fgraph`)\n\n- `dotnet build \u002Fgraph` or `msbuild \u002Fgraph`\n- What it changes: MSBuild constructs the full project dependency graph BEFORE building\n- Benefits: better scheduling, avoids redundant evaluations, enables isolated builds\n- Limitations: all projects must use `\u003CProjectReference>` (no programmatic MSBuild task references)\n- When to use: large solutions with many projects, CI builds\n- When NOT to use: projects that dynamically discover references at build time\n\n## Optimizing Project References\n\n- Reduce unnecessary `\u003CProjectReference>` — each adds to the dependency chain\n- Use `\u003CProjectReference ... SkipGetTargetFrameworkProperties=\"true\">` to avoid extra evaluations\n- `\u003CProjectReference ... ReferenceOutputAssembly=\"false\">` for build-order-only dependencies\n- Consider if a ProjectReference should be a PackageReference instead (pre-built NuGet)\n- Use `solution filters` (`.slnf`) to build subsets of the solution\n\n## BuildInParallel\n\n- `\u003CMSBuild Projects=\"@(ProjectsToBuild)\" BuildInParallel=\"true\" \u002F>` in custom targets\n- Without `BuildInParallel=\"true\"`, MSBuild task batches projects sequentially\n- Ensure `\u002Fmaxcpucount` > 1 for this to have effect\n\n## Multi-threaded MSBuild Tasks\n\n- Individual tasks can run multi-threaded within a single project build\n- Tasks implementing `IMultiThreadableTask` can run on multiple threads\n- Tasks must declare thread-safety via `[MSBuildMultiThreadableTask]`\n\n## Analyzing Parallelism with Binlog\n\n### Primary: binlog MCP (preferred)\n\nUse the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace):\n\n1. Use expensive_projects tool → find the slowest projects and compare individual vs total build time\n2. Use expensive_targets tool → find bottleneck targets\n3. Use project_target_times tool → drill into a specific project's target-level timing\n4. Ideal: build time should be much less than sum of project times (parallelism)\n5. If build time ≈ sum of project times: too many serial dependencies, or one slow project blocking others\n\n### Fallback: text-log replay (when MCP is unavailable)\n\nStep-by-step:\n\n1. Replay the binlog: `dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary`\n2. Check Project Performance Summary at the end of `full.log`\n3. Ideal: build time should be much less than sum of project times (parallelism)\n4. If build time ≈ sum of project times: too many serial dependencies, or one slow project blocking others\n5. `grep 'Target Performance Summary' -A 30 full.log` → find the bottleneck targets\n6. Consider splitting large projects or optimizing the critical path\n\n## CI\u002FCD Parallelism Tips\n\n- Use `-m` in CI (many CI runners have multiple cores)\n- Consider splitting solution into build stages for extreme parallelism\n- Use build caching (NuGet lock files, deterministic builds) to avoid rebuilding unchanged projects\n- `dotnet build \u002Fgraph` works well with structured CI pipelines\n",{"data":35,"body":36},{"name":4,"description":6,"license":25},{"type":37,"children":38},"root",[39,48,54,181,187,243,249,293,306,359,365,429,435,474,480,512,518,525,552,580,586,591,640,646],{"type":40,"tag":41,"props":42,"children":44},"element","h2",{"id":43},"diagnose-a-slow-parallel-build-start-here",[45],{"type":46,"value":47},"text","Diagnose a slow parallel build (start here)",{"type":40,"tag":49,"props":50,"children":51},"p",{},[52],{"type":46,"value":53},"Work this checklist in order — it targets the usual root cause (a serial\ndependency chain that no number of cores can parallelize):",{"type":40,"tag":55,"props":56,"children":57},"ol",{},[58,102,112,137,163],{"type":40,"tag":59,"props":60,"children":61},"li",{},[62,68,70,77,79,85,87,93,95,100],{"type":40,"tag":63,"props":64,"children":65},"strong",{},[66],{"type":46,"value":67},"Confirm parallelism is even on.",{"type":46,"value":69}," Rebuild with ",{"type":40,"tag":71,"props":72,"children":74},"code",{"className":73},[],[75],{"type":46,"value":76},"dotnet build -m \u002Fbl:{}",{"type":46,"value":78},"\n(PowerShell: ",{"type":40,"tag":71,"props":80,"children":82},{"className":81},[],[83],{"type":46,"value":84},"dotnet build -m -bl:{{}}",{"type":46,"value":86},"). ",{"type":40,"tag":71,"props":88,"children":90},{"className":89},[],[91],{"type":46,"value":92},"-m",{"type":46,"value":94}," with no number uses all logical\nprocessors; without ",{"type":40,"tag":71,"props":96,"children":98},{"className":97},[],[99],{"type":46,"value":92},{"type":46,"value":101}," MSBuild runs a single node (sequential).",{"type":40,"tag":59,"props":103,"children":104},{},[105,110],{"type":40,"tag":63,"props":106,"children":107},{},[108],{"type":46,"value":109},"Find the critical path.",{"type":46,"value":111}," From the binlog, read per-project timings and the\nnode timeline. If total build time ≈ the sum of the projects on one\ndependency chain, that chain — not CPU count — is the bottleneck.",{"type":40,"tag":59,"props":113,"children":114},{},[115,120,122,128,130,135],{"type":40,"tag":63,"props":116,"children":117},{},[118],{"type":46,"value":119},"Name the chain explicitly",{"type":46,"value":121},", e.g. ",{"type":40,"tag":71,"props":123,"children":125},{"className":124},[],[126],{"type":46,"value":127},"Core → Api → Web → Tests",{"type":46,"value":129},". A long serial\nchain stays serial no matter how large ",{"type":40,"tag":71,"props":131,"children":133},{"className":132},[],[134],{"type":46,"value":92},{"type":46,"value":136}," is, because each project waits on\nits predecessor.",{"type":40,"tag":59,"props":138,"children":139},{},[140,153,155,161],{"type":40,"tag":63,"props":141,"children":142},{},[143,145,151],{"type":46,"value":144},"Look for unnecessary ",{"type":40,"tag":71,"props":146,"children":148},{"className":147},[],[149],{"type":46,"value":150},"ProjectReference",{"type":46,"value":152}," edges",{"type":46,"value":154}," that lengthen the chain — a\nreference that only needs build order (not the output assembly), or one that\ncould be a ",{"type":40,"tag":71,"props":156,"children":158},{"className":157},[],[159],{"type":46,"value":160},"PackageReference",{"type":46,"value":162},", forces serialization it doesn't need.",{"type":40,"tag":59,"props":164,"children":165},{},[166,171,173,179],{"type":40,"tag":63,"props":167,"children":168},{},[169],{"type":46,"value":170},"Recommend flattening",{"type":46,"value":172},": break false dependencies so independent projects\nbuild concurrently, and consider ",{"type":40,"tag":71,"props":174,"children":176},{"className":175},[],[177],{"type":46,"value":178},"\u002Fgraph",{"type":46,"value":180}," for better scheduling.",{"type":40,"tag":41,"props":182,"children":184},{"id":183},"msbuild-parallelism-model",[185],{"type":46,"value":186},"MSBuild Parallelism Model",{"type":40,"tag":188,"props":189,"children":190},"ul",{},[191,209,221,233,238],{"type":40,"tag":59,"props":192,"children":193},{},[194,200,202,207],{"type":40,"tag":71,"props":195,"children":197},{"className":196},[],[198],{"type":46,"value":199},"\u002Fmaxcpucount",{"type":46,"value":201}," (or ",{"type":40,"tag":71,"props":203,"children":205},{"className":204},[],[206],{"type":46,"value":92},{"type":46,"value":208},"): number of worker nodes (processes)",{"type":40,"tag":59,"props":210,"children":211},{},[212,214,219],{"type":46,"value":213},"Default: 1 node (sequential!). Always use ",{"type":40,"tag":71,"props":215,"children":217},{"className":216},[],[218],{"type":46,"value":92},{"type":46,"value":220}," for parallel builds",{"type":40,"tag":59,"props":222,"children":223},{},[224,226,231],{"type":46,"value":225},"Recommended: ",{"type":40,"tag":71,"props":227,"children":229},{"className":228},[],[230],{"type":46,"value":92},{"type":46,"value":232}," without a number = use all logical processors",{"type":40,"tag":59,"props":234,"children":235},{},[236],{"type":46,"value":237},"Each node builds one project at a time",{"type":40,"tag":59,"props":239,"children":240},{},[241],{"type":46,"value":242},"Projects are scheduled based on dependency graph",{"type":40,"tag":41,"props":244,"children":246},{"id":245},"project-dependency-graph",[247],{"type":46,"value":248},"Project Dependency Graph",{"type":40,"tag":188,"props":250,"children":251},{},[252,257,262,267,288],{"type":40,"tag":59,"props":253,"children":254},{},[255],{"type":46,"value":256},"MSBuild builds projects in dependency order (topological sort)",{"type":40,"tag":59,"props":258,"children":259},{},[260],{"type":46,"value":261},"Critical path: longest chain of dependent projects determines minimum build time",{"type":40,"tag":59,"props":263,"children":264},{},[265],{"type":46,"value":266},"Bottleneck: if project A depends on B, C, D and B takes 60s while C and D take 5s, B is the bottleneck",{"type":40,"tag":59,"props":268,"children":269},{},[270,272,278,280,286],{"type":46,"value":271},"Diagnosis: replay binlog to diagnostic log with ",{"type":40,"tag":71,"props":273,"children":275},{"className":274},[],[276],{"type":46,"value":277},"performancesummary",{"type":46,"value":279}," and check Project Performance Summary — shows per-project time; grep for ",{"type":40,"tag":71,"props":281,"children":283},{"className":282},[],[284],{"type":46,"value":285},"node.*assigned",{"type":46,"value":287}," to check scheduling",{"type":40,"tag":59,"props":289,"children":290},{},[291],{"type":46,"value":292},"Wide graphs (many independent projects) parallelize well; deep graphs (long chains) don't",{"type":40,"tag":41,"props":294,"children":296},{"id":295},"graph-build-mode-graph",[297,299,304],{"type":46,"value":298},"Graph Build Mode (",{"type":40,"tag":71,"props":300,"children":302},{"className":301},[],[303],{"type":46,"value":178},{"type":46,"value":305},")",{"type":40,"tag":188,"props":307,"children":308},{},[309,326,331,336,349,354],{"type":40,"tag":59,"props":310,"children":311},{},[312,318,320],{"type":40,"tag":71,"props":313,"children":315},{"className":314},[],[316],{"type":46,"value":317},"dotnet build \u002Fgraph",{"type":46,"value":319}," or ",{"type":40,"tag":71,"props":321,"children":323},{"className":322},[],[324],{"type":46,"value":325},"msbuild \u002Fgraph",{"type":40,"tag":59,"props":327,"children":328},{},[329],{"type":46,"value":330},"What it changes: MSBuild constructs the full project dependency graph BEFORE building",{"type":40,"tag":59,"props":332,"children":333},{},[334],{"type":46,"value":335},"Benefits: better scheduling, avoids redundant evaluations, enables isolated builds",{"type":40,"tag":59,"props":337,"children":338},{},[339,341,347],{"type":46,"value":340},"Limitations: all projects must use ",{"type":40,"tag":71,"props":342,"children":344},{"className":343},[],[345],{"type":46,"value":346},"\u003CProjectReference>",{"type":46,"value":348}," (no programmatic MSBuild task references)",{"type":40,"tag":59,"props":350,"children":351},{},[352],{"type":46,"value":353},"When to use: large solutions with many projects, CI builds",{"type":40,"tag":59,"props":355,"children":356},{},[357],{"type":46,"value":358},"When NOT to use: projects that dynamically discover references at build time",{"type":40,"tag":41,"props":360,"children":362},{"id":361},"optimizing-project-references",[363],{"type":46,"value":364},"Optimizing Project References",{"type":40,"tag":188,"props":366,"children":367},{},[368,380,393,404,409],{"type":40,"tag":59,"props":369,"children":370},{},[371,373,378],{"type":46,"value":372},"Reduce unnecessary ",{"type":40,"tag":71,"props":374,"children":376},{"className":375},[],[377],{"type":46,"value":346},{"type":46,"value":379}," — each adds to the dependency chain",{"type":40,"tag":59,"props":381,"children":382},{},[383,385,391],{"type":46,"value":384},"Use ",{"type":40,"tag":71,"props":386,"children":388},{"className":387},[],[389],{"type":46,"value":390},"\u003CProjectReference ... SkipGetTargetFrameworkProperties=\"true\">",{"type":46,"value":392}," to avoid extra evaluations",{"type":40,"tag":59,"props":394,"children":395},{},[396,402],{"type":40,"tag":71,"props":397,"children":399},{"className":398},[],[400],{"type":46,"value":401},"\u003CProjectReference ... ReferenceOutputAssembly=\"false\">",{"type":46,"value":403}," for build-order-only dependencies",{"type":40,"tag":59,"props":405,"children":406},{},[407],{"type":46,"value":408},"Consider if a ProjectReference should be a PackageReference instead (pre-built NuGet)",{"type":40,"tag":59,"props":410,"children":411},{},[412,413,419,421,427],{"type":46,"value":384},{"type":40,"tag":71,"props":414,"children":416},{"className":415},[],[417],{"type":46,"value":418},"solution filters",{"type":46,"value":420}," (",{"type":40,"tag":71,"props":422,"children":424},{"className":423},[],[425],{"type":46,"value":426},".slnf",{"type":46,"value":428},") to build subsets of the solution",{"type":40,"tag":41,"props":430,"children":432},{"id":431},"buildinparallel",[433],{"type":46,"value":434},"BuildInParallel",{"type":40,"tag":188,"props":436,"children":437},{},[438,449,462],{"type":40,"tag":59,"props":439,"children":440},{},[441,447],{"type":40,"tag":71,"props":442,"children":444},{"className":443},[],[445],{"type":46,"value":446},"\u003CMSBuild Projects=\"@(ProjectsToBuild)\" BuildInParallel=\"true\" \u002F>",{"type":46,"value":448}," in custom targets",{"type":40,"tag":59,"props":450,"children":451},{},[452,454,460],{"type":46,"value":453},"Without ",{"type":40,"tag":71,"props":455,"children":457},{"className":456},[],[458],{"type":46,"value":459},"BuildInParallel=\"true\"",{"type":46,"value":461},", MSBuild task batches projects sequentially",{"type":40,"tag":59,"props":463,"children":464},{},[465,467,472],{"type":46,"value":466},"Ensure ",{"type":40,"tag":71,"props":468,"children":470},{"className":469},[],[471],{"type":46,"value":199},{"type":46,"value":473}," > 1 for this to have effect",{"type":40,"tag":41,"props":475,"children":477},{"id":476},"multi-threaded-msbuild-tasks",[478],{"type":46,"value":479},"Multi-threaded MSBuild Tasks",{"type":40,"tag":188,"props":481,"children":482},{},[483,488,501],{"type":40,"tag":59,"props":484,"children":485},{},[486],{"type":46,"value":487},"Individual tasks can run multi-threaded within a single project build",{"type":40,"tag":59,"props":489,"children":490},{},[491,493,499],{"type":46,"value":492},"Tasks implementing ",{"type":40,"tag":71,"props":494,"children":496},{"className":495},[],[497],{"type":46,"value":498},"IMultiThreadableTask",{"type":46,"value":500}," can run on multiple threads",{"type":40,"tag":59,"props":502,"children":503},{},[504,506],{"type":46,"value":505},"Tasks must declare thread-safety via ",{"type":40,"tag":71,"props":507,"children":509},{"className":508},[],[510],{"type":46,"value":511},"[MSBuildMultiThreadableTask]",{"type":40,"tag":41,"props":513,"children":515},{"id":514},"analyzing-parallelism-with-binlog",[516],{"type":46,"value":517},"Analyzing Parallelism with Binlog",{"type":40,"tag":519,"props":520,"children":522},"h3",{"id":521},"primary-binlog-mcp-preferred",[523],{"type":46,"value":524},"Primary: binlog MCP (preferred)",{"type":40,"tag":49,"props":526,"children":527},{},[528,530,535,536,542,544,550],{"type":46,"value":529},"Use the ",{"type":40,"tag":63,"props":531,"children":532},{},[533],{"type":46,"value":534},"binlog MCP server",{"type":46,"value":420},{"type":40,"tag":71,"props":537,"children":539},{"className":538},[],[540],{"type":46,"value":541},"Microsoft.AITools.BinlogMcp",{"type":46,"value":543},", exposed under the ",{"type":40,"tag":71,"props":545,"children":547},{"className":546},[],[548],{"type":46,"value":549},"binlog",{"type":46,"value":551}," MCP namespace):",{"type":40,"tag":55,"props":553,"children":554},{},[555,560,565,570,575],{"type":40,"tag":59,"props":556,"children":557},{},[558],{"type":46,"value":559},"Use expensive_projects tool → find the slowest projects and compare individual vs total build time",{"type":40,"tag":59,"props":561,"children":562},{},[563],{"type":46,"value":564},"Use expensive_targets tool → find bottleneck targets",{"type":40,"tag":59,"props":566,"children":567},{},[568],{"type":46,"value":569},"Use project_target_times tool → drill into a specific project's target-level timing",{"type":40,"tag":59,"props":571,"children":572},{},[573],{"type":46,"value":574},"Ideal: build time should be much less than sum of project times (parallelism)",{"type":40,"tag":59,"props":576,"children":577},{},[578],{"type":46,"value":579},"If build time ≈ sum of project times: too many serial dependencies, or one slow project blocking others",{"type":40,"tag":519,"props":581,"children":583},{"id":582},"fallback-text-log-replay-when-mcp-is-unavailable",[584],{"type":46,"value":585},"Fallback: text-log replay (when MCP is unavailable)",{"type":40,"tag":49,"props":587,"children":588},{},[589],{"type":46,"value":590},"Step-by-step:",{"type":40,"tag":55,"props":592,"children":593},{},[594,605,616,620,624,635],{"type":40,"tag":59,"props":595,"children":596},{},[597,599],{"type":46,"value":598},"Replay the binlog: ",{"type":40,"tag":71,"props":600,"children":602},{"className":601},[],[603],{"type":46,"value":604},"dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary",{"type":40,"tag":59,"props":606,"children":607},{},[608,610],{"type":46,"value":609},"Check Project Performance Summary at the end of ",{"type":40,"tag":71,"props":611,"children":613},{"className":612},[],[614],{"type":46,"value":615},"full.log",{"type":40,"tag":59,"props":617,"children":618},{},[619],{"type":46,"value":574},{"type":40,"tag":59,"props":621,"children":622},{},[623],{"type":46,"value":579},{"type":40,"tag":59,"props":625,"children":626},{},[627,633],{"type":40,"tag":71,"props":628,"children":630},{"className":629},[],[631],{"type":46,"value":632},"grep 'Target Performance Summary' -A 30 full.log",{"type":46,"value":634}," → find the bottleneck targets",{"type":40,"tag":59,"props":636,"children":637},{},[638],{"type":46,"value":639},"Consider splitting large projects or optimizing the critical path",{"type":40,"tag":41,"props":641,"children":643},{"id":642},"cicd-parallelism-tips",[644],{"type":46,"value":645},"CI\u002FCD Parallelism Tips",{"type":40,"tag":188,"props":647,"children":648},{},[649,660,665,670],{"type":40,"tag":59,"props":650,"children":651},{},[652,653,658],{"type":46,"value":384},{"type":40,"tag":71,"props":654,"children":656},{"className":655},[],[657],{"type":46,"value":92},{"type":46,"value":659}," in CI (many CI runners have multiple cores)",{"type":40,"tag":59,"props":661,"children":662},{},[663],{"type":46,"value":664},"Consider splitting solution into build stages for extreme parallelism",{"type":40,"tag":59,"props":666,"children":667},{},[668],{"type":46,"value":669},"Use build caching (NuGet lock files, deterministic builds) to avoid rebuilding unchanged projects",{"type":40,"tag":59,"props":671,"children":672},{},[673,678],{"type":40,"tag":71,"props":674,"children":676},{"className":675},[],[677],{"type":46,"value":317},{"type":46,"value":679}," works well with structured CI pipelines",{"items":681,"total":786},[682,697,712,730,744,764,774],{"slug":683,"name":683,"fn":684,"description":685,"org":686,"tags":687,"stars":22,"repoUrl":23,"updatedAt":696},"analyzing-dotnet-performance","analyze .NET code for performance anti-patterns","Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I\u002FO with tiered severity classification. Use when analyzing .NET code for optimization opportunities, reviewing hot paths, or auditing allocation-heavy patterns.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[688,689,692,695],{"name":17,"slug":18,"type":15},{"name":690,"slug":691,"type":15},"Code Analysis","code-analysis",{"name":693,"slug":694,"type":15},"Debugging","debugging",{"name":13,"slug":14,"type":15},"2026-07-12T08:23:25.400375",{"slug":698,"name":698,"fn":699,"description":700,"org":701,"tags":702,"stars":22,"repoUrl":23,"updatedAt":711},"android-tombstone-symbolication","symbolicate .NET runtime frames in Android tombstones","Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app crash from a tombstone, resolving native backtrace frames in libmonosgen-2.0.so or libcoreclr.so to .NET runtime source code, or investigating SIGABRT, SIGSEGV, or other native signals originating from the .NET runtime on Android. DO NOT USE FOR pure Java\u002FKotlin crashes, managed .NET exceptions that are already captured in logcat, or iOS crash logs. INVOKES Symbolicate-Tombstone.ps1 script, llvm-symbolizer, Microsoft symbol server.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[703,704,707,708],{"name":17,"slug":18,"type":15},{"name":705,"slug":706,"type":15},"Android","android",{"name":693,"slug":694,"type":15},{"name":709,"slug":710,"type":15},"Microsoft","microsoft","2026-07-12T08:23:21.595572",{"slug":713,"name":713,"fn":714,"description":715,"org":716,"tags":717,"stars":22,"repoUrl":23,"updatedAt":729},"apple-crash-symbolication","symbolicate .NET runtime frames in crash logs","Symbolicate .NET runtime frames in Apple platform .ips crash logs (iOS, tvOS, Mac Catalyst, macOS). Extracts UUIDs and addresses from the native backtrace, locates dSYM debug symbols, and runs atos to produce function names with source file and line numbers. Automatically downloads .dwarf symbols from the Microsoft symbol server using Mach-O UUIDs. USE FOR triaging a .NET MAUI or Mono app crash from an .ips file on any Apple platform, resolving native backtrace frames in libcoreclr or libmonosgen-2.0 to .NET runtime source code, retrieving .ips crash logs from a connected iOS device or iPhone, or investigating EXC_CRASH, EXC_BAD_ACCESS, SIGABRT, or SIGSEGV originating from the .NET runtime. DO NOT USE FOR pure Swift\u002FObjective-C crashes with no .NET components, or Android tombstone files. INVOKES Symbolicate-Crash.ps1 script, atos, dwarfdump, idevicecrashreport.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[718,719,720,723,726],{"name":17,"slug":18,"type":15},{"name":693,"slug":694,"type":15},{"name":721,"slug":722,"type":15},"iOS","ios",{"name":724,"slug":725,"type":15},"macOS","macos",{"name":727,"slug":728,"type":15},"Observability","observability","2026-07-12T08:23:20.369986",{"slug":731,"name":731,"fn":732,"description":733,"org":734,"tags":735,"stars":22,"repoUrl":23,"updatedAt":743},"assertion-quality","evaluate assertion quality in test suites","Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow tests, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull \u002F toBeTruthy()), flag self-referential or tautological assertions, measure assertion diversity, or audit whether tests verify different facets of behavior. Polyglot: .NET, Python, TS\u002FJS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. DO NOT USE FOR: writing new tests (use code-testing-agent \u002F writing-mstest-tests), mutation reasoning about whether tests would catch a bug (use test-gap-analysis), or a general severity-ranked anti-pattern audit (use test-anti-patterns), fixing or rewriting assertions, or writing, fixing, or modernizing MSTest tests, assertions, or attributes (use writing-mstest-tests).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[736,737,740],{"name":690,"slug":691,"type":15},{"name":738,"slug":739,"type":15},"QA","qa",{"name":741,"slug":742,"type":15},"Testing","testing","2026-07-12T08:23:51.277743",{"slug":745,"name":745,"fn":746,"description":747,"org":748,"tags":749,"stars":22,"repoUrl":23,"updatedAt":763},"author-component","create and review Blazor components","Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable, CancellationToken, CSS isolation, code-behind. DO NOT USE FOR: creating new projects (use create-blazor-project), JavaScript interop or calling browser APIs from Blazor (use use-js-interop), forms and validation (use collect-user-input), prerendering issues (use support-prerendering), HTTP data fetching patterns (use fetch-and-send-data), coordinating state between unrelated components (use coordinate-components).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[750,751,754,757,760],{"name":17,"slug":18,"type":15},{"name":752,"slug":753,"type":15},"Blazor","blazor",{"name":755,"slug":756,"type":15},"C#","csharp",{"name":758,"slug":759,"type":15},"UI Components","ui-components",{"name":761,"slug":762,"type":15},"Web Development","web-development","2026-07-15T06:03:29.216359",{"slug":765,"name":765,"fn":766,"description":767,"org":768,"tags":769,"stars":22,"repoUrl":23,"updatedAt":773},"binlog-failure-analysis","analyze MSBuild binary logs","Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[770,771,772],{"name":690,"slug":691,"type":15},{"name":693,"slug":694,"type":15},{"name":709,"slug":710,"type":15},"2026-07-12T08:21:34.637923",{"slug":775,"name":775,"fn":776,"description":777,"org":778,"tags":779,"stars":22,"repoUrl":23,"updatedAt":785},"binlog-generation","generate MSBuild binary logs for diagnostics","Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding \u002Fbl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ \u002F .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[780,783,784],{"name":781,"slug":782,"type":15},"Build","build",{"name":693,"slug":694,"type":15},{"name":20,"slug":21,"type":15},"2026-07-19T05:38:19.340791",96,{"items":788,"total":889},[789,801,808,815,823,829,837,843,849,855,868,879],{"slug":790,"name":790,"fn":791,"description":792,"org":793,"tags":794,"stars":798,"repoUrl":799,"updatedAt":800},"multithreaded-task-migration","migrate MSBuild tasks to multithreaded mode","Guide for migrating MSBuild tasks to multithreaded mode support, including compatibility red-team review. Use this when converting tasks to thread-safe versions, implementing IMultiThreadableTask, adding TaskEnvironment support, or auditing migrations for behavioral compatibility.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[795,796,797],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},5535,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fmsbuild","2026-07-22T05:37:33.965588",{"slug":683,"name":683,"fn":684,"description":685,"org":802,"tags":803,"stars":22,"repoUrl":23,"updatedAt":696},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[804,805,806,807],{"name":17,"slug":18,"type":15},{"name":690,"slug":691,"type":15},{"name":693,"slug":694,"type":15},{"name":13,"slug":14,"type":15},{"slug":698,"name":698,"fn":699,"description":700,"org":809,"tags":810,"stars":22,"repoUrl":23,"updatedAt":711},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[811,812,813,814],{"name":17,"slug":18,"type":15},{"name":705,"slug":706,"type":15},{"name":693,"slug":694,"type":15},{"name":709,"slug":710,"type":15},{"slug":713,"name":713,"fn":714,"description":715,"org":816,"tags":817,"stars":22,"repoUrl":23,"updatedAt":729},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[818,819,820,821,822],{"name":17,"slug":18,"type":15},{"name":693,"slug":694,"type":15},{"name":721,"slug":722,"type":15},{"name":724,"slug":725,"type":15},{"name":727,"slug":728,"type":15},{"slug":731,"name":731,"fn":732,"description":733,"org":824,"tags":825,"stars":22,"repoUrl":23,"updatedAt":743},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[826,827,828],{"name":690,"slug":691,"type":15},{"name":738,"slug":739,"type":15},{"name":741,"slug":742,"type":15},{"slug":745,"name":745,"fn":746,"description":747,"org":830,"tags":831,"stars":22,"repoUrl":23,"updatedAt":763},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[832,833,834,835,836],{"name":17,"slug":18,"type":15},{"name":752,"slug":753,"type":15},{"name":755,"slug":756,"type":15},{"name":758,"slug":759,"type":15},{"name":761,"slug":762,"type":15},{"slug":765,"name":765,"fn":766,"description":767,"org":838,"tags":839,"stars":22,"repoUrl":23,"updatedAt":773},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[840,841,842],{"name":690,"slug":691,"type":15},{"name":693,"slug":694,"type":15},{"name":709,"slug":710,"type":15},{"slug":775,"name":775,"fn":776,"description":777,"org":844,"tags":845,"stars":22,"repoUrl":23,"updatedAt":785},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[846,847,848],{"name":781,"slug":782,"type":15},{"name":693,"slug":694,"type":15},{"name":20,"slug":21,"type":15},{"slug":4,"name":4,"fn":5,"description":6,"org":850,"tags":851,"stars":22,"repoUrl":23,"updatedAt":24},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[852,853,854],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},{"slug":856,"name":856,"fn":857,"description":858,"org":859,"tags":860,"stars":22,"repoUrl":23,"updatedAt":867},"build-perf-baseline","establish and optimize build performance baselines","Establish build performance baselines and apply systematic optimization techniques. USE FOR: diagnosing slow builds, establishing before\u002Fafter measurements (cold, warm, no-op scenarios), applying optimization strategies like MSBuild Server, static graph builds, artifacts output, and dependency graph trimming. Start here before diving into build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE FOR: non-MSBuild build systems, detailed bottleneck analysis (use build-perf-diagnostics after baselining).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[861,862,865,866],{"name":20,"slug":21,"type":15},{"name":863,"slug":864,"type":15},"Monitoring","monitoring",{"name":13,"slug":14,"type":15},{"name":741,"slug":742,"type":15},"2026-07-12T08:21:35.865649",{"slug":869,"name":869,"fn":870,"description":871,"org":872,"tags":873,"stars":22,"repoUrl":23,"updatedAt":878},"build-perf-diagnostics","diagnose MSBuild build performance bottlenecks","Diagnose MSBuild build performance bottlenecks using binary log analysis. 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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[874,875,876,877],{"name":17,"slug":18,"type":15},{"name":693,"slug":694,"type":15},{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},"2026-07-12T08:21:40.961722",{"slug":880,"name":880,"fn":881,"description":882,"org":883,"tags":884,"stars":22,"repoUrl":23,"updatedAt":888},"check-bin-obj-clash","detect MSBuild output path conflicts","Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing\u002Foverwritten outputs in multi-project or multi-targeting builds where bin\u002Fobj (or project.assets.json) collide. Common causes: shared OutputPath, missing AppendTargetFrameworkToOutputPath, extra global properties (e.g. PublishReadyToRun), or SetTargetFramework on a ProjectReference to a single-targeting project. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[885,886,887],{"name":693,"slug":694,"type":15},{"name":20,"slug":21,"type":15},{"name":738,"slug":739,"type":15},"2026-07-19T05:38:14.336279",144]