dotnet-audit

Audit .NET projects for missing quality tooling, hooks, and CI coverage.

2|1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ondrasek/cc-plugins --skill dotnet-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-audit
Source: https://github.com/ondrasek/cc-plugins/tree/main/plugins/blueprint/skills/dotnet-audit
Command: npx skills add https://github.com/ondrasek/cc-plugins --skill dotnet-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a fast, read-only gap analysis that identifies missing quality tooling, hook coverage, and CI jobs in .NET repositories so teams know what to configure before onboarding or improvement work.

Core Features & Use Cases

  • Project Inventory: Detects .NET SDK and target framework versions, solution layout, and framework usage.
  • Configuration Audit: Inspects Directory.Build.props, .editorconfig, and .csproj files for quality-related settings and flags gaps against a 9-dimension methodology.
  • Hook & CI Coverage: Verifies expected hooks (SessionStart, PostToolUse/Edit|Write, Stop) and CI jobs (test, lint, security, version) and surfaces missing items with recommendations.
  • Use Case: Use this Skill when preparing to run automated setup, during codebase health checks, or before releasing to ensure required quality tooling and pipelines are in place.

Quick Start

Run the dotnet-audit skill to analyze a .NET repository and produce a gap analysis report of quality dimensions, hooks, and CI coverage.

Frequently Asked Questions about dotnet-audit

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

FAQPage Schema
How do I audit a .NET project for missing quality tooling and CI gaps?▼

To audit a .NET project, run a read-only gap analysis that inspects SDK versions, Directory.Build.props, .editorconfig, and .csproj files. This detects missing quality tooling, hook coverage, and CI jobs, providing a per-dimension report of gaps and recommended setup actions.

What is a .NET codebase quality audit and when do I need one?▼

A .NET codebase quality audit evaluates repository health by checking configuration files and CI coverage against a 9-dimension methodology. You need this audit during pre-setup onboarding, periodic quality reviews, or before releasing to ensure required tooling and pipelines are in place.

How do I check if my .NET solution has missing CI jobs and hooks?▼

You can check for missing CI jobs and hooks by verifying expected configurations like test, lint, security, and version jobs, alongside hooks like SessionStart and PostToolUse. The audit surfaces missing items and provides recommendations for complete CI coverage.

Can I use this audit on any .NET SDK project or solution?▼

This audit applies specifically to .NET SDK projects and solutions. It detects SDK and target framework versions, inventories solution layout, and inspects framework usage to ensure the quality setup analysis is accurately scoped to your repository's configuration.

Does the .NET audit modify my repository files during the quality review?▼

The .NET audit is a fast, read-only gap analysis that does not modify your repository files. It inspects configuration files and CI settings to produce a report of quality dimensions, hooks, and coverage gaps without altering your codebase.

What's the best way to prepare a .NET repository for automated quality setup?▼

The best way to prepare is to run a pre-setup audit that inventories Directory.Build.props, .editorconfig, and .csproj settings. This identifies missing tooling and framework gaps, ensuring you know exactly what to configure before onboarding automated setup work.