Repair .NET solution build and test failures with Docker integration tests.
npx skills add https://github.com/mpaulosky/dotfiles --skill build-repair
Please help me install this Agent Skill. Skill: build-repair Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/build-repair Command: npx skills add https://github.com/mpaulosky/dotfiles --skill build-repair
Provides a repeatable, authoritative process to diagnose and repair build and test failures for the IssueManager .NET solution so developers and CI pipelines do not land broken commits.
Ask the assistant to run the build-repair process on IssueManager by restoring packages, building the solution, running Release tests, and reporting errors with suggested fixes.
High-intent search queries and answers about installing and using this skill.
To fix .NET build failures, follow an iterative restore, build, and test sequence with zero-warning tolerance. Restore NuGet packages first, then build the solution, referencing Directory.Packages.props to resolve version conflicts until the build is clean.
.NET integration tests fail in CI when Docker is not running because TestContainers requires Docker to provision dependencies. Ensure Docker is installed and active in your CI environment before running integration tests to avoid container provisioning failures.
To resolve NuGet version conflicts, reference the Directory.Packages.props file to centralize package versioning. Apply an iterative build repair workflow that enforces zero warnings to catch and fix mismatched package references across the entire .NET solution.
The best way to troubleshoot flaky .NET tests is applying targeted failure signatures for port conflicts, CI path issues, and equality assertions. Run unit, integration, architecture, and web tests iteratively to isolate intermittent failures.
Yes, your CI pipeline needs Docker to run .NET integration tests that use TestContainers. Docker provides the isolated environments required for integration testing, so you must verify Docker availability in your CI environment before executing the test suite.
When your .NET Release build produces warnings, apply a strict zero-tolerance repair workflow by restoring packages, rebuilding, and running tests iteratively. Address each warning individually until the solution builds cleanly with zero warnings and zero test failures.
Im5tuCentralize NuGet package versions in .NET solutions via Directory.Packages.props.
DavidLam-ossAutomate versioning, validation, and deployment for Obsidian plugins.
seb1nAutomate build, test, and deployment pipelines across multiple platforms.
NotMyselfManage .NET 10 projects with standard dotnet CLI commands.
