Use only for MSBuild failure investigation, build-performance analysis, or review of existing build XML/extension contracts.
MSBuild Anti-Pattern Catalog
DO NOT INVOKE when the primary request explicitly asks to convert, migrate, modernize, or rewrite a legacy/old-style project to SDK style; use msbuild-modernization. Migration prompts often mention ToolsVersion, explicit Compile/Reference entries, packages.config, or Microsoft.CSharp.targets, but merely reviewing or auditing a file that contains those patterns remains in scope here. USE FOR broad review, audit, lint, or maintainability/correctness checks of project/build files, including custom targets; prioritized cross-cutting findings; discrete anti-patterns; F# ordering/FS0039; cross-platform paths; and focused Import safety verdicts. Review/audit is analysis-only unless fixes are requested. For concrete property/item defects use property-patterns/item-management; use target-authoring for implementation and extension-points for NuGet auto-import/layout discovery. Exclude non-MSBuild systems.
Related skills
Analyze MSBuild binary logs to diagnose build failures.
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis.
Building AI agents on .NET?
Managed Code builds production AI agents in C# and .NET.