analyze

Analyzes .NET projects for unused packages, quality issues, and vulnerabilities via dotnet tooling.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cooper538/eshop-demo --skill analyze-cooper538
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/cooper538/eshop-demo/tree/main/.claude/skills/analyze
Command: npx skills add https://github.com/cooper538/eshop-demo --skill analyze-cooper538

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly identify unused NuGet packages, code quality issues, and security vulnerabilities in a codebase, reducing technical debt and speeding up feedback loops.

Core Features & Use Cases

  • Unused Package Discovery: Detects and reports packages that are no longer referenced in the solution.
  • Quality & Style Checks: Flags Roslyn warnings, code smells, and potential refactor targets.
  • Security Assessment: Scans dependencies for known CVEs and deprecated components.
  • Use Case: Integrate into CI to surface actionable items before merges.

Quick Start

Run the analyze tool in your project with /analyze to perform a full scan, or use /analyze quality for a focused quality check.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I find unused NuGet packages and security vulnerabilities in a .NET solution?

To find unused NuGet packages and security vulnerabilities in a .NET solution, you can run an automated code analysis scan that checks dependencies against known CVEs and reports unreferenced packages to reduce technical debt.

Can I run code quality and style checks across multi-project .NET solutions?

Yes, you can run code quality and style checks across multi-project .NET solutions to flag Roslyn warnings, identify code smells, and highlight potential refactor targets within the codebase.

What is the best way to automate dependency security scanning for .NET in CI workflows?

The best way to automate dependency security scanning for .NET in CI workflows is to integrate a codebase analyzer that executes under tools/analyzers to surface actionable vulnerability items before merges.

Do I need dotnet tooling installed to analyze code health and detect deprecated components?

Yes, you need dotnet tooling installed and must run dotnet tool restore to analyze code health, as the process relies on this environment to detect deprecated components and execute the required scripts.

How do I perform a focused code quality check instead of a full codebase scan?

To perform a focused code quality check instead of a full codebase scan, execute the analyzer with the quality option, which isolates Roslyn warnings and refactor targets while skipping package and security assessments.

What security risks and code quality issues does .NET code analysis detect?

.NET code analysis detects unused packages, code smells, Roslyn warnings, and security risks including known CVEs and deprecated components, providing a comprehensive assessment of codebase health.