dotnet-build-analysis

Analyze MSBuild output and diagnose CS, MSB, NU, IDE, and CA errors.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-build-analysis-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-build-analysis
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-build-analysis
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-build-analysis-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers understand and resolve complex build errors, NuGet restore failures, and analyzer warnings that commonly plague .NET projects, especially in CI/CD environments.

Core Features & Use Cases

  • Error Code Interpretation: Deciphers prefixes like CS, MSB, NU, IDE, and CA to pinpoint the source of build issues.
  • Restore Failure Diagnosis: Guides users through common NuGet restore problems like missing packages or version conflicts.
  • CI Drift Resolution: Provides patterns to fix issues that appear only in Continuous Integration environments.
  • Use Case: You encounter an error MSB4019 during your build. This Skill explains that it's an MSBuild engine error, likely due to a missing SDK or workload, and suggests checking your .csproj file's SDK declaration and running dotnet workload list.

Quick Start

Use the dotnet-build-analysis skill to interpret the MSBuild error 'MSB4019: The imported project was not found'.

Frequently Asked Questions about dotnet-build-analysis

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

FAQPage Schema
How do I fix MSBuild error MSB4019 when the imported project is not found?

MSBuild error MSB4019 occurs when a referenced SDK or workload is missing. Check your .csproj file's SDK declaration and run dotnet workload list to verify required components are installed.

What do the CS, MSB, NU, IDE, and CA prefixes mean in .NET build errors?

These prefixes pinpoint error sources: CS for C# compiler errors, MSB for MSBuild engine errors, NU for NuGet package errors, IDE for code style diagnostics, and CA for .NET code analysis warnings.

Why does my NuGet package restore fail due to version conflicts in CI/CD?

NuGet restore version conflicts often stem from CI drift or missing packages. Diagnose by analyzing the NU error codes in your build output and resolving dependency version mismatches locally.

How do I resolve multi-targeting build failures in SDK-style projects?

Resolve multi-targeting build failures by interpreting the build output to identify target framework conflicts. Check your SDK-style project configurations and ensure all specified target frameworks have required dependencies.

What is the best way to troubleshoot Roslyn analyzer warnings during a build?

Troubleshoot Roslyn analyzer warnings by reading the CA diagnostic codes in your build output. These .NET code analysis warnings highlight rule violations, and you can apply suggested fix patterns to resolve them.

Can I use this to diagnose CI drift issues that only appear in continuous integration environments?

Yes, you can diagnose CI drift by comparing local and CI build outputs. Analyzing the MSBuild and NuGet errors helps identify missing SDKs or environment configurations causing continuous integration failures.