dotnet-project-analysis

Analyze .NET solution structure, project references, and build configuration.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-project-analysis-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-project-analysis
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-project-analysis
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-project-analysis-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly understand the structure, dependencies, and build configuration of any .NET project, making it easier to navigate and contribute to codebases.

Core Features & Use Cases

  • Solution & Project Discovery: Identifies .sln, .slnx, and .csproj files to map out the project hierarchy.
  • Dependency Mapping: Visualizes project references to understand relationships.
  • Build Configuration Analysis: Detects shared settings from Directory.Build.props, Directory.Packages.props, and nuget.config.
  • Use Case: When you clone a new .NET repository, use this Skill to get an immediate overview of its architecture, identify the main entry points, and understand how packages are managed.

Quick Start

Analyze the current .NET project structure and report key findings.

Frequently Asked Questions about dotnet-project-analysis

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

FAQPage Schema
How do I analyze .NET project structure and dependencies in a new repository?

To analyze .NET project structure, parse .sln, .slnx, and .csproj files to map project hierarchies, identify project types, and visualize dependency graphs for web, console, worker, Blazor, and MAUI applications.

What is centralized package management in .NET and how do I detect it?

Centralized package management (CPM) in .NET is detected by analyzing Directory.Packages.props files, which centralize NuGet versioning across multiple projects instead of defining versions in individual .csproj files.

How do I find entry points for Blazor and MAUI applications in a .NET solution?

Find entry points for Blazor and MAUI applications by scanning .csproj files within the .NET solution to identify specific project types, output configurations, and dependency relationships.

Can I use Directory.Build.props to understand shared build configurations across projects?

Yes, you can understand shared build configurations by parsing Directory.Build.props files, which define common MSBuild properties and settings applied across multiple .NET projects within a solution hierarchy.