What problem does it solve? MSBuild builds fail intermittently with errors like "Cannot create a file when that file already exists" or "file is being used by another process" when multiple project evaluations write to the same bin/obj output directories, and the root cause is hard to pinpoint without structured analysis. ## Core Features & Use Cases - Clash Detection via Binlog MCP: Query binary logs with MCP tools (evaluations, evaluation_global_properties, double_writes) to find evaluations sharing OutputPath or IntermediateOutputPath. - Text-Log Fallback Workflow: Replay the binlog to a diagnostic text log and grep for evaluation counts, output paths, and distinguishing global properties when the MCP server is unavailable. - Root-Cause Catalog with Fixes: Covers multi-targeting without TargetFramework in path, shared BaseIntermediateOutputPath across projects, RuntimeIdentifier clashes, multi-solution builds, extra global properties like PublishReadyToRun or _IsPublishing, and redundant SetTargetFramework on ProjectReference. - Use Case: A parallel build fails during NuGet restore with "Cannot create a file when that file already exists"; this skill inspects the binlog, finds two projects sharing one IntermediateOutputPath where project.assets.json is written, and prescribes unique per-project obj paths. ## Quick Start Generate a binary log of the failing build and use this skill to check whether any MSBuild project evaluations share the same OutputPath or IntermediateOutputPath.
