build-perf-diagnostics Skill
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 belo Published by microsoft in testfx.
What is build-perf-diagnostics Skill?
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 belo Published by microsoft in testfx. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use build-perf-diagnostics Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .agents/skills/build-perf-diagnostics/SKILL.md
What it does
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 belo
Skill instructions
Performance Analysis Methodology 1. Generate a binlog: dotnet build /bl:{} -m 2. Use the binlog MCP server (Microsoft.AITools.BinlogMcp, exposed under the binlog MCP namespace) which is bundled with this plugin Alternate flow when MCP is unavailable: binlog replay to text logs 1. Generate a binlog: dotnet build /bl:{} -m 2. Replay to diagnostic log with performance summary: bash dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log;performancesummary 3. Read the performance summary (at the end of full.log): bash grep "Target Performance Summary|Task Performance Summary" -A 50 full.log 4. Find expensive targets and tasks: The PerformanceSummary section lists all targets/tasks sorted by cumulative time 5. Check for node utilization: grep for scheduling and node messages bash grep -i "node.assigned|building with|scheduler" full.log | head -30 6. Check analyzers: grep for analyzer timing bash grep -i "analyzer.elapsed|Total analyzer execution time|CompilerAnalyzerDriv
Explore related resources
Frequently asked questions
What is build-perf-diagnostics?
build-perf-diagnostics is a open-source AI agent skill with Copy skill directory. Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference.
Who is build-perf-diagnostics best for?
build-perf-diagnostics is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install build-perf-diagnostics?
Install or run build-perf-diagnostics using Copy skill directory. Check build-perf-diagnostics for the latest setup command.
Is build-perf-diagnostics actively maintained?
build-perf-diagnostics may need a closer maintenance check before production use.
Auto-fetched from GitHub.
