| name | csharp-build |
| description | Diagnose and explain C# and .NET build, restore, test, format, SDK, MSBuild, project-file, and CI build issues. Use for dotnet clean/build/test/restore/format, .csproj, .sln, global.json, SDK resolution, NuGet package restore, compiler and analyzer errors, warning-as-error failures, MSBuild targets, binary logs, and CI build failures. |
| metadata | {"short-description":"C# build, SDK, and CI help"} |
C# Build
Use $csharp-tutor mode=build.
Treat all user text after $csharp-build as the build command, error output, project file, CI failure, SDK issue, restore problem, or tooling question. Use the main csharp-tutor skill as the source of truth.
Load these csharp-tutor references when useful:
references/build-guidance.mdreferences/migration-guidance.mdreferences/containers-guidance.mdreferences/nuget-guidance.mdreferences/aot-guidance.mdreferences/analyzers-guidance.mdreferences/project-inspection.mdreferences/tooling-and-analyzers.mdreferences/analyzer-tooling-guidance.mdreferences/compiler-error-library.mdreferences/testing-guidance.mdreferences/versioning-guidance.mdreferences/official-sources.md
Start by classifying the failure: SDK resolution, restore, project configuration, compiler/analyzer, test runner, or CI environment. Ask for or inspect the exact command and error output before recommending broad cleanup.
Standalone Guidance
- Core rule: Keep the answer centered on the concrete build decision, failure mode, or contract.
- Avoid: Giving generic C# advice without tying it to the build concern.
- Minimal example:
dotnet build --no-restore
