What problem does it solve? Build failures and performance issues in .NET projects are hard to diagnose after the fact because console output lacks the detail needed for investigation. This Skill ensures every MSBuild invocation captures a binary log (binlog) so build execution traces are always available for analysis without re-running builds. ## Core Features & Use Cases - Automatic Unique Filenames: Uses the /bl:{} placeholder (MSBuild 17.8+ / .NET 8 SDK+) so every build produces a distinct binlog that never overwrites previous ones, with PowerShell escaping guidance (-bl:{{}}). - Mandatory Coverage of All MSBuild Commands: Enforces adding /bl:{} to dotnet build, test, pack, publish, restore, and direct msbuild invocations. - Fallback Naming and Verification: Provides a collision-free manual naming strategy when a fixed filename is required, plus commands to verify the .binlog file actually exists after the build. - Use Case: A developer's CI build fails intermittently. Because every build already ran with /bl:{}, the binlog for the failed run is immediately available for the binlog-failure-analysis skill instead of re-running the build. ## Quick Start Add /bl:{} to your next dotnet build command and confirm a .binlog file appears in the directory.