check-bin-obj-clash

Detect MSBuild output path conflicts in bin/obj directories from binary logs.

Updated May 28, 2026
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill check-bin-obj-clash-ojrojas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-bin-obj-clash
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-msbuild/skills/check-bin-obj-clash
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill check-bin-obj-clash-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires binlog MCP server tools, dotnet msbuild, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and diagnoses conflicts in MSBuild output paths, preventing build failures and ensuring smooth builds.

Core Features & Use Cases

  • Detects OutputPath and IntermediateOutputPath Clashes: Identifies when multiple MSBuild projects write to the same bin/obj directories.
  • Binlog Analysis: Inspects binary logs for conflicts without parsing text logs.
  • Fallback to Text-Log Replay: Provides a fallback method for analyzing text logs when the MCP server is unavailable.
  • Detailed Reporting: Reports all evaluations with conflicting paths and suggests potential fixes.
  • Use Case: When you encounter build failures with 'Cannot create a file when that file already exists' or intermittent build failures, this Skill can help diagnose and resolve the issue.

Quick Start

Use the check-bin-obj-clash skill to analyze the binary log from your last build and identify any conflicting output paths.

Frequently Asked Questions about check-bin-obj-clash

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

FAQPage Schema
Why does my MSBuild fail with 'Cannot create a file when that file already exists'?

Intermittent MSBuild failures typically stem from multiple projects writing to the same bin/obj directories. Analyzing binary logs detects these IntermediateOutputPath clashes and provides detailed reports to resolve the conflicts.

How do I diagnose MSBuild output path conflicts using a binary log?

To diagnose MSBuild output path conflicts, inspect your binary logs using binlog MCP server tools to identify overlapping OutputPath and IntermediateOutputPath directories, which prevents build failures and ensures smooth builds.

Can I analyze MSBuild build conflicts without the binlog MCP server?

Yes, you can analyze MSBuild build conflicts without the binlog MCP server by using a fallback text-log replay method to inspect logs and identify overlapping output paths.

What is the best way to find multiple MSBuild projects writing to the same bin or obj directories?

The best way to find projects writing to the same bin or obj directories is to inspect binary logs for conflicting OutputPath and IntermediateOutputPath evaluations, generating detailed reports with suggested fixes.

Does check-bin-obj-clash work with dotnet msbuild?

Yes, the check-bin-obj-clash skill works with dotnet msbuild, requiring access to MSBuild binary logs and MCP server tools to detect and diagnose output path conflicts effectively.

What are the limitations of using text-log replay for MSBuild binary log analysis?

Text-log replay is a fallback for analyzing MSBuild build conflicts when the MCP server is unavailable, but parsing text logs may be less efficient than direct binary log analysis for identifying output path clashes.