dotnet-meziantou-analyzer

Name: dotnet-meziantou-analyzer
Availability: InStock
Author: postpartum-genushyacinthus29

Integrate Meziantou.Analyzer into a .NET project and configure its rules.

8|Updated Mar 29, 2026

Search Tags:#security #dotnet #code-quality #analyze #analyzers #meziantou

Ready to run

npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-meziantou-analyzer-postpartum-genushyacinthus29

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-meziantou-analyzer
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-meziantou-analyzer
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-meziantou-analyzer-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates and enforces broad .NET code-quality rules by installing and configuring Meziantou.Analyzer across a repository, reducing code smells and unsafe patterns.

Core Features & Use Cases

Unified analyzer package for design, usage, security, performance, and style rules.
Guided bootstrap: detect existing analyzer references, add the NuGet package, and align root severities in .editorconfig.
Workflow-driven improvements: plan, implement, and validate analyzer changes with explicit artifacts and verification.

Quick Start

Install and run the skill to bootstrap Meziantou.Analyzer in your repository and review the resulting diagnostics.

Frequently Asked Questions about dotnet-meziantou-analyzer

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

FAQPage Schema

How do I add Meziantou.Analyzer to a .NET project to check code quality and security?▼

To add Meziantou.Analyzer to a .NET project, the skill detects existing analyzer references, adds the NuGet package, and guides severity configuration in .editorconfig to enforce code quality and security rules.

What rules does Meziantou.Analyzer cover for .NET repositories?▼

Meziantou.Analyzer covers broad .NET rules for design, usage, security, performance, and style, consolidating code-quality checks to reduce code smells and unsafe patterns across your repository.

Can I configure .editorconfig severities when applying analyzers across a .NET codebase?▼

Yes, you can configure .editorconfig severities when applying analyzers. The skill guides root severity alignment to ensure consistent rule enforcement across the entire .NET codebase.

Does this analyzer setup workflow validate against repository configuration files?▼

Yes, the analyzer setup validates changes against the repository's AGENTS.md and .editorconfig files, ensuring the integrated code-quality rules align with existing project configurations.

What is the best way to enforce consistent .NET code style rules in CI pipelines?▼

The best way to enforce .NET code style rules in CI pipelines is using a workflow that plans, implements, and validates analyzer changes with explicit artifacts, ensuring broad rule coverage and consistent checks.

Why should I use a unified .NET analyzer package instead of individual analyzers?▼

Using a unified .NET analyzer package provides broad rule coverage for design, security, performance, and style in one step, simplifying setup and ensuring consistent code-quality validation across repositories.