dotnet-project-analysis

Analyze .NET solution and project configurations, including references and build settings.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-project-analysis-rudironsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-project-analysis
Source: https://github.com/rudironsoni/dotnet-agent-harness/tree/main/.rulesync/skills/dotnet-project-analysis
Command: npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-project-analysis-rudironsoni

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, which is crucial before making any code changes.

Core Features & Use Cases

  • Solution & Project Discovery: Locates .sln, .slnx, and .csproj files.
  • Dependency Mapping: Visualizes project references and identifies potential issues.
  • Configuration Analysis: Detects Central Package Management (CPM), Directory.Build.props, and nuget.config settings.
  • Use Case: Before refactoring a large .NET solution, use this Skill to get a clear map of all projects, their interdependencies, and shared build configurations.

Quick Start

Analyze the .NET solution structure and project dependencies in the current directory.

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 solution structure and project dependencies before refactoring?

Mapping .NET project dependencies involves locating .sln, .slnx, and .csproj files to visualize project references. This process identifies project types, test projects, and entry points to clarify interdependencies before code changes.

What is Central Package Management and how does it affect .NET build configuration?

Central Package Management (CPM) in .NET build configuration centralizes NuGet package versions across projects. It is detected alongside Directory.Build.props and nuget.config files to enforce consistent dependency versions throughout the solution.

Can I use project analysis to find entry points and test projects in a .NET solution?

Yes, .NET project analysis identifies application entry points and test projects by examining .csproj files. It detects various .NET application types and their specific configurations to clarify the solution's execution and testing structure.

How do I locate and interpret .editorconfig, nuget.config, and global.json settings in a .NET project?

Locating .editorconfig, nuget.config, and global.json settings requires scanning the .NET project directory for these configuration files. The analysis detects their presence and interprets their impact on build settings, package management, and code style.

What's the best way to visualize project references across multiple .NET csproj files?

The best way to visualize project references across .NET csproj files is to parse the solution and project files to construct a dependency graph. This maps all interdependencies and highlights potential reference issues within the solution.