project-inspection

Query MSBuild properties and items from .csproj files to diagnose project configuration.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill project-inspection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-inspection
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/skills/project-inspection
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill project-inspection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MSBuild and project-file inspection for .csproj files to help diagnose and understand project configuration, targets, and references.

Core Features & Use Cases

  • Evaluate MSBuild properties for a project and surface key values like TargetFramework, OutputType, and Nullable.
  • Inspect item lists such as PackageReference and ProjectReference to understand dependencies and packaging.
  • Validate project shape and consistency across a workspace, producing per-project checks and remediation hints when mismatches occur.

Quick Start

Resolve the active workspace and the path to your .csproj, then query properties or items to inspect configuration.

Frequently Asked Questions about project-inspection

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

FAQPage Schema
How do I inspect MSBuild properties in a .csproj file?

Inspect MSBuild properties in a .csproj file by querying evaluated values to reveal project configuration details like TargetFramework, OutputType, and Nullable. This works for both SDK-style and legacy projects.

Can I check PackageReference and ProjectReference items across an entire workspace?

Check PackageReference and ProjectReference items across an entire workspace by evaluating MSBuild item lists for each project. This surfaces dependencies and packaging configurations to help validate consistency.

What is the best way to diagnose TargetFramework and OutputPath mismatches in a .NET workspace?

Diagnose TargetFramework and OutputPath mismatches by validating project shape and consistency across the workspace. This produces per-project checks and remediation hints when configuration mismatches occur.

Does this MSBuild project inspection approach work with legacy csproj files?

MSBuild project inspection works with both SDK-style and legacy .csproj files. It evaluates properties and items read-only, applying safely across single-project files or entire workspaces without modifying configurations.

Why do I need to evaluate MSBuild properties instead of just reading the raw csproj XML?

Evaluate MSBuild properties instead of reading raw XML to resolve conditional declarations and imported values. This reveals the effective project configuration, exposing evaluated properties that raw XML alone does not show.

What are the limitations of read-only MSBuild project inspection?

Read-only MSBuild project inspection is limited to diagnosing and understanding configuration. It evaluates properties and items with a safety posture that prevents modifying project files, meaning remediation is provided as hints rather than applied changes.