What problem does it solve? Build failures and performance issues in .NET projects are hard to diagnose without a detailed record of what MSBuild actually did. This Skill ensures every dotnet build, test, pack, publish, or restore command captures a binary log (binlog) so failures can be investigated without re-running the build. ## Core Features & Use Cases - Automatic binlog capture: Adds the /bl:{} flag to any MSBuild-based command so every build produces a diagnostic trace. - Unique file naming: Uses the {} placeholder (MSBuild 17.8+ / .NET 8 SDK+) so each build writes a distinct binlog and never overwrites previous ones, with PowerShell escaping guidance (-bl:{{}}). - Fallback naming and cleanup safety: Provides incrementing filename strategies when {} is unavailable and preserves binlogs during git clean with -e "*.binlog". - Use Case: A CI build fails intermittently. Because every build already ran with /bl:{}, the binlog for the failed run is immediately available for analysis with the binlog-failure-analysis skill instead of reproducing the failure. ## Quick Start Add the /bl:{} flag to my dotnet build command so it generates a binary log for diagnostics.