dotnet-msbuild

Diagnoses and optimizes MSBuild builds for classic .csproj projects.

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/aggutierrez98/TP-TD --skill dotnet-msbuild-aggutierrez98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-msbuild
Source: https://github.com/aggutierrez98/TP-TD/tree/main/.agents/skills/dotnet-msbuild
Command: npx skills add https://github.com/aggutierrez98/TP-TD --skill dotnet-msbuild-aggutierrez98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Build failures, slow builds, and broken project references in classic-format .csproj solutions are hard to diagnose from console logs alone. This Skill provides structured MSBuild diagnostics, from binary log analysis to anti-pattern detection, so you can pinpoint root causes and optimize build performance. ## Core Features & Use Cases - Binlog Failure Analysis: Generate a .binlog from a failed build and query it through the binlog MCP server to trace error cascades instead of guessing from console output. - Build Performance Diagnostics: Establish timing baselines, identify expensive targets, fix non-incremental targets, and enable parallel builds with the /m flag. - Anti-Pattern Review: Scan .csproj files for hardcoded paths, unquoted conditions, monolithic targets, and bin/obj folder clashes. - Use Case: Your TpIDS.sln build fails with a vague error. Generate a .binlog with msbuild TpIDS.sln /bl, analyze it via the binlog MCP tools, fix the broken ProjectReference, then verify the solution compiles. ## Quick Start Ask the AI to diagnose why the TpIDS solution build is failing by generating and analyzing an MSBuild binary log.

Frequently Asked Questions about dotnet-msbuild

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

FAQPage Schema
How do I diagnose a vague MSBuild build failure?▼

Generate a binary log by running msbuild with the /bl flag, for example `msbuild TpIDS.sln /bl`. Then analyze the .binlog file using the binlog MCP server tools to trace the error cascade instead of reading raw console output.

How to speed up a slow MSBuild build?▼

Start by establishing a timing baseline, then identify expensive targets and unnecessary I/O. Enable parallel builds with the /m flag, fix targets that lack proper inputs/outputs for incremental support, and consider the MSBuild server to reduce startup time.

Does this work with SDK-style .csproj projects?▼

The Skill targets the classic .csproj format with explicit Compile Include entries and TargetFrameworkVersion v4.7.2. Migration to SDK-style is only performed when explicitly requested, and the manual file listing anti-pattern does not apply to classic format.

Why are my MSBuild targets not building incrementally?▼

Targets run fully when they lack correctly declared Inputs and Outputs attributes, causing MSBuild to consider them always out of date. Author targets with proper inputs/outputs and check for file timestamp issues or unconditional copy tasks.

What are common MSBuild anti-patterns in .csproj files?▼

Common anti-patterns include hardcoded absolute paths, conditions without quotes, monolithic targets doing too much work, and bin/obj folder clashes between projects. Reviewing .csproj files for these patterns prevents fragile and non-portable builds.