build-perf-diagnostics

Analyze MSBuild binary logs to identify performance bottlenecks and optimization areas.

Updated May 28, 2026
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill build-perf-diagnostics-ojrojas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-perf-diagnostics
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-msbuild/skills/build-perf-diagnostics
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill build-perf-diagnostics-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill diagnoses and identifies performance bottlenecks in MSBuild build processes by analyzing binary logs, helping users to improve the speed and efficiency of their builds.

Core Features & Use Cases

  • Binlog Analysis: Diagnose MSBuild build performance bottlenecks using binary log analysis.
  • Contextual Use: Only activates in MSBuild/.NET build context.
  • Features: Identifies slow MSBuild operations, detects issues like long RAR processing, analyzes compiler analyzer time, identifies dominant targets and tasks, checks node utilization, and provides performance summaries.
  • Use Case: Use after establishing baseline measurements with build-perf-baseline. Not suitable for baseline establishment, incremental build issues, or non-MSBuild systems.

Quick Start

Use the build-perf-diagnostics skill to analyze build performance issues by replaying the binlog for a build with the command dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary.

Frequently Asked Questions about build-perf-diagnostics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze MSBuild build performance using a binlog file?

You can analyze MSBuild build performance by replaying a binary log file using the command `dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary` to generate a diagnostic log and performance summary for interpretation.

What specific build performance bottlenecks can I identify with binary log analysis?

Binary log analysis identifies slow MSBuild operations, long RAR processing, excessive compiler analyzer time, and dominant targets or tasks. It also checks node utilization and provides a comprehensive performance summary.

Does MSBuild binary log analysis work for non-.NET build systems?

No, binary log analysis for build performance diagnostics is applicable only within MSBuild and .NET contexts. It is not suitable for diagnosing build performance issues in non-MSBuild systems or for resolving incremental build problems.

Do I need a baseline measurement before diagnosing MSBuild build performance?

Yes, you should establish baseline measurements using a separate baseline process before running build performance diagnostics. This Skill is designed to diagnose bottlenecks after a baseline is established, not to create the initial baseline or handle incremental build issues.