check-bin-obj-clash Skill
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi Published by microsoft in testfx.
What is check-bin-obj-clash Skill?
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi Published by microsoft in testfx. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using testfx
Technical details
- Install or run with Copy skill directory
When to use check-bin-obj-clash Skill
- Use it for developers using testfx.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .agents/skills/check-bin-obj-clash/SKILL.md
What it does
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi
Skill instructions
Detecting OutputPath and IntermediateOutputPath Clashes Overview This skill helps identify when multiple MSBuild project evaluations share the same OutputPath or IntermediateOutputPath. This is a common source of build failures including: - File access conflicts during parallel builds - Missing or overwritten output files - Intermittent build failures - "File in use" errors - NuGet restore errors like Cannot create a file when that file already exists - this strongly indicates multiple projects share the same IntermediateOutputPath where project.assets.json is written Clashes can occur between: - Different projects sharing the same output directory - Multi-targeting builds (e.g., TargetFrameworks=net8.0;net9.0) where the path doesn't include the target framework - Multiple solution builds where the same project is built from different solutions in a single build Note: Project instances with BuildProjectReferences=false should be ignored when analyzing clashes - these are P2P reference
Explore related resources
Frequently asked questions
What is check-bin-obj-clash?
check-bin-obj-clash is a open-source AI agent skill with Copy skill directory. Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath.
Who is check-bin-obj-clash best for?
check-bin-obj-clash is best for reusing agent instructions, scripts, and references.
How do I install check-bin-obj-clash?
Install or run check-bin-obj-clash using Copy skill directory. Check check-bin-obj-clash for the latest setup command.
Is check-bin-obj-clash actively maintained?
check-bin-obj-clash may need a closer maintenance check before production use.
Auto-fetched from GitHub.
