meziantou-analyzer

This skill installs and configures Meziantou.Analyzer, a comprehensive rule set for .NET codebases covering design, usage, security, performance, and style concerns. It manages package setup, severity configuration in `.editorconfig`, and avoids duplication with SDK or Roslynator analyzers. Use it when your team wants broader diagnostic coverage without managing multiple analyzer packages.

Meziantou.Analyzer adds design, security, performance, and style rules to .NET projects via a single NuGet package.

AI-generated summary based on this skill's SKILL.md

★ 463 ⁮ 35 MIT updated 2026-07-25 by managedcode

Install

managedcode/dotnet-skills/meziantou-analyzer · repository language: C#

Manual (git clone) CLI (skillfed)

git clone https://github.com/managedcode/dotnet-skills
cp -r dotnet-skills/catalog/Tools/Meziantou-Analyzer/skills/meziantou-analyzer ~/.claude/skills/meziantou-analyzer

npx skillfed install managedcode/dotnet-skills/meziantou-analyzer

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

How do I add meziantou analyzer to a dotnet project?

meziantou-analyzer is installed as a NuGet package. Run `dotnet add package Meziantou.Analyzer` in your project directory, or add `<PackageReference Include="Meziantou.Analyzer" />` to your .csproj file. The package automatically integrates with your build and enables design, security, performance, and style rules across your codebase.

How do I configure meziantou analyzer severity in .editorconfig?

meziantou-analyzer rules use the MA prefix and are configured in `.editorconfig` at your repository root. Set severity per rule: `dotnet_diagnostic.MA0001.severity = warning`. Create a `[*.cs]` section and list each rule's desired level (none, silent, suggestion, warning, error). This ensures team consistency without modifying individual project files.

Does meziantou analyzer overlap with existing analyzer baselines?

meziantou-analyzer can overlap with SDK analyzers and Roslynator. Review your current analyzer rules before enabling Meziantou to avoid duplicate diagnostics. Disable conflicting rules in `.editorconfig` by setting their severity to `none`, or choose one analyzer suite per concern area. This keeps CI output actionable and prevents rule fatigue.

What code quality rules does meziantou analyzer enforce?

meziantou-analyzer covers design patterns, usage best practices, security concerns, performance optimizations, and code style. Rules span naming conventions, null-safety, async patterns, LINQ efficiency, and more. Each rule is identified by an MA code (e.g., MA0001) and can be individually configured in `.editorconfig` to match your team's standards.

How should I bootstrap meziantou analyzer for CI validation?

Start by installing the package and running a full build to see all diagnostics. Triage rules in `.editorconfig`: set high-priority violations to `error` for CI gates, medium concerns to `warning`, and style preferences to `suggestion`. Test locally first, then enable in CI pipelines. This prevents build failures while gradually enforcing standards.

When should I use meziantou analyzer vs Roslynator?

meziantou-analyzer provides broader coverage across design, security, and performance in a single package, making it ideal for teams wanting comprehensive diagnostics without managing multiple analyzers. Roslynator focuses more on refactoring suggestions. Choose Meziantou for strict enforcement or Roslynator for enhancement-oriented analysis; avoid running both on overlapping rules.

SKILL.md

rendered from the published skill — quoted content, verbatim