tech-preflight-dotnet

Verify .NET SDK compatibility and map solution references before code changes.

53|27|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/andresharpe/dotbot --skill tech-preflight-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-preflight-dotnet
Source: https://github.com/andresharpe/dotbot/tree/main/stacks/dotnet/recipes/skills/tech-preflight-dotnet
Command: npx skills add https://github.com/andresharpe/dotbot --skill tech-preflight-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents avoidable build failures by validating your local .NET SDK environment against what your solution targets, then capturing a baseline state before any code changes happen.

Core Features & Use Cases

  • SDK/runtime compatibility verification: Compares installed SDKs from dotnet --list-sdks with all TargetFramework and TargetFrameworks values across .csproj files to flag gaps and assess rollforward viability.
  • Dependency graph mapping: Runs dotnet list {solution}.sln reference to identify project reference relationships and potential layering violations, including circular dependencies.
  • Baseline build capture: Executes dotnet build {solution}.sln and records error/warning counts plus messages so later failures can be distinguished from pre-existing issues.
  • Use cases: onboarding to a .NET solution, starting new tasks safely, or diagnosing build failures caused by SDK mismatches or architectural reference direction problems.

Quick Start

Run tech-preflight-dotnet to validate SDK compatibility, map the solution’s project reference graph, and capture a baseline dotnet build for comparison after changes.

Frequently Asked Questions about tech-preflight-dotnet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my installed .NET SDKs match my project's target frameworks?

To check .NET SDK compatibility, compare the output of dotnet --list-sdks against the TargetFramework and TargetFrameworks values across your .csproj files. This identifies SDK gaps and assesses rollforward viability before you start coding.

What is the best way to map circular dependencies in a .NET solution?

Mapping circular dependencies in a .NET solution involves running dotnet list reference against the .sln file. This identifies project reference relationships and flags potential architectural layering violations or circular dependencies.

Why does my dotnet build fail on a new machine during onboarding?

Your dotnet build may fail during onboarding due to SDK gaps where installed SDKs do not match the TargetFramework requirements. Running preflight checks validates the local .NET SDK environment and flags missing runtimes before code changes.

How do I capture a baseline .NET build before making code changes?

To capture a baseline .NET build, execute dotnet build on your solution file and record the error and warning counts with their messages. This establishes a pre-change state to distinguish new failures from pre-existing issues.

Can I detect multi-targeting framework issues in .NET before building?

Yes, you can detect multi-targeting issues by verifying installed SDKs against all TargetFrameworks specified in your .csproj files. This preflight check flags SDK gaps and assesses rollforward viability before the build starts.

What are the limitations of using dotnet list reference for architecture layering checks?

Using dotnet list reference maps project reference relationships and flags circular dependencies, but it only provides a dependency graph assessment. It does not automatically fix architectural layering violations or resolve SDK compatibility gaps.