dotnet-tooling

Analyzes .NET repository structure and build metadata to recommend improvements.

46|7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill dotnet-tooling-sunyonghuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-tooling
Source: https://github.com/sunyonghuan/Netor.Madorin/tree/main/.github/skills/dotnet-tooling
Command: npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill dotnet-tooling-sunyonghuan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you understand, configure, and modernize .NET repositories without guessing at SDK, MSBuild, packaging, or runtime choices. It is designed for teams that need reliable guidance on project structure, build performance, AOT readiness, CLI distribution, and day-to-day developer tooling.

Core Features & Use Cases

  • Project and build setup: Decide on solution layout, Directory.Build settings, central package management, analyzers, and artifacts output.
  • Performance and compatibility: Diagnose build slowdowns, multi-targeting gaps, trimming issues, Native AOT constraints, and GC or memory concerns.
  • Developer workflows: Improve CLI app architecture, debug configuration, documentation tooling, IL decompilation, and release packaging.
  • Use case: A .NET team can use this Skill to review an existing repo, identify modernization opportunities, and produce concrete changes for build files, target frameworks, and release pipelines.

Quick Start

Use the dotnet-tooling skill to analyze the repository structure and recommend the best .NET SDK, build, packaging, and modernization actions for this project.

Frequently Asked Questions about dotnet-tooling

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

FAQPage Schema
How do I configure .NET central package management and Directory.Build.props for a multi-targeting solution?

To configure .NET central package management, you analyze repository metadata like Directory.Packages.props and Directory.Build.props to recommend SDK, MSBuild, and multi-targeting changes that standardize project structure and build outputs.

What is the best way to diagnose .NET build slowdowns and Native AOT trimming issues?

Diagnosing .NET build slowdowns and Native AOT constraints requires inspecting .csproj files and build artifacts to identify performance bottlenecks, trimming issues, and memory concerns, producing concrete modernization guidance.

Does Native AOT work with existing .NET CLI tooling and packaging pipelines?

Native AOT compatibility depends on your specific .NET repository structure and build metadata. Analyzing your solution layout, target frameworks, and CLI architecture determines AOT readiness and identifies necessary release pipeline adjustments.

How do I modernize an existing .NET repository's SDK and analyzer configuration?

Modernizing a .NET repository involves reviewing solution layout, build files, and analyzer configuration to recommend SDK upgrades, packaging improvements, and developer tooling enhancements for your release pipelines.

Why does my .NET multi-targeting build fail when switching target frameworks?

.NET multi-targeting build failures often stem from misconfigured Directory.Build.props or missing package references. Inspecting repository build metadata and project structure identifies multi-targeting gaps and recommends corrective MSBuild changes.