build-parallelism Skill
Guide for optimizing MSBuild build parallelism and multi-project scheduling. USE FOR: builds not utilizing all CPU cores, speeding up multi-project solutions, evaluating graph build mode (/graph), build time not improving with -m flag, understanding project dependency topology. Note: /maxcpucount default is 1 (sequenti Published by microsoft in testfx.
What is build-parallelism Skill?
Guide for optimizing MSBuild build parallelism and multi-project scheduling. USE FOR: builds not utilizing all CPU cores, speeding up multi-project solutions, evaluating graph build mode (/graph), build time not improving with -m flag, understanding project dependency topology. Note: /maxcpucount default is 1 (sequenti 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
- Developers using testfx
Technical details
- Install or run with Copy skill directory
When to use build-parallelism Skill
- Use it for developers using testfx.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .agents/skills/build-parallelism/SKILL.md
What it does
Guide for optimizing MSBuild build parallelism and multi-project scheduling. USE FOR: builds not utilizing all CPU cores, speeding up multi-project solutions, evaluating graph build mode (/graph), build time not improving with -m flag, understanding project dependency topology. Note: /maxcpucount default is 1 (sequenti
Skill instructions
MSBuild Parallelism Model - /maxcpucount (or -m): number of worker nodes (processes) - Default: 1 node (sequential!). Always use -m for parallel builds - Recommended: -m without a number = use all logical processors - Each node builds one project at a time - Projects are scheduled based on dependency graph Project Dependency Graph - MSBuild builds projects in dependency order (topological sort) - Critical path: longest chain of dependent projects determines minimum build time - Bottleneck: if project A depends on B, C, D and B takes 60s while C and D take 5s, B is the bottleneck - Diagnosis: replay binlog to diagnostic log with performancesummary and check Project Performance Summary — shows per-project time; grep for node.assigned to check scheduling - Wide graphs (many independent projects) parallelize well; deep graphs (long chains) don't Graph Build Mode (/graph) - dotnet build /graph or msbuild /graph - What it changes: MSBuild constructs the full project dependency graph BEFORE b
Explore related resources
Frequently asked questions
What is build-parallelism?
build-parallelism is a open-source AI agent skill with Copy skill directory. Guide for optimizing MSBuild build parallelism and multi-project scheduling. USE FOR: builds not utilizing all CPU cores, speeding up multi-project solutions, evaluating graph build mode (/graph).
Who is build-parallelism best for?
build-parallelism is best for reusing agent instructions, scripts, and references.
How do I install build-parallelism?
Install or run build-parallelism using Copy skill directory. Check build-parallelism for the latest setup command.
Is build-parallelism actively maintained?
build-parallelism may need a closer maintenance check before production use.
Auto-fetched from GitHub.
