Use only for MSBuild failure investigation, build-performance analysis, or review of existing build XML/extension contracts.
Performance Analysis Methodology
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/Task 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.
Related skills
Analyze MSBuild binary logs to diagnose build failures.
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis.
Building AI agents on .NET?
Managed Code builds production AI agents in C# and .NET.