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
Decision gist · record as of 2026-07-25
Meziantou.Analyzer adds design, security, performance, and style rules to .NET projects via a single NuGet package. 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.
Use it when
- meziantou-analyzer rules use the MA prefix and are configured in `.editorconfig` at your repository root.
- meziantou-analyzer can overlap with SDK analyzers and Roslynator.
Verify before relying
Read SKILL.md below before installing (5 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/meziantou-analyzer · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
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.
Meziantou.Analyzer
Trigger On
- the repo uses or wants
Meziantou.Analyzer - the team wants one analyzer pack that covers design, usage, security, performance, and style
Value
- produce a concrete project delta: code, docs, config, tests, CI, or review artifact
- reduce ambiguity through explicit planning, verification, and final validation skills
- leave reusable project context so future tasks are faster and
(truncated - see the full file via the links below)
File tree — 5 files
catalog/Tools/Meziantou-Analyzer/skills/meziantou-analyzer/SKILL.md
catalog/Tools/Meziantou-Analyzer/skills/meziantou-analyzer/manifest.json
catalog/Tools/Meziantou-Analyzer/skills/meziantou-analyzer/references/config.md
catalog/Tools/Meziantou-Analyzer/skills/meziantou-analyzer/references/meziantou-analyzer.md
catalog/Tools/Meziantou-Analyzer/skills/meziantou-analyzer/references/rules.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Add and configure Meziantou.Analyzer package to enforce design, security, and performance rules”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Roslynator equips .NET projects with open-source static analysis and code-cleanup capabilities through NuGet analyzer packages and an optional command-line tool. Configure rule severity in `.editorconfig`, run analysis and fix workflows, or detect unused code—all while respecting your repo's existing analyzer setup.
cloc delivers line-count, language composition, and branch-diff statistics for .NET codebases through repeatable, configurable commands. Use it to measure solution footprint, compare code deltas across refs, and track codebase composition—not to assess developer productivity or replace design review.
This skill establishes a single source of truth for .NET analyzer severity and code-style rules by creating or normalizing a repo-root .editorconfig file. It detects your current configuration state, structures rule ownership explicitly, and validates that settings are reproducible across local and CI builds.
stylecop-analyzers sets up the StyleCop.Analyzers package in .NET repositories, establishing clear ownership between root .editorconfig and stylecop.json configuration. It detects existing state, adds the package where needed, and prevents rule overlap with other analyzer packs. Use it when your team requires stronger style conventions than SDK analyzers alone provide.
This skill sets up the .NET SDK's built-in Roslyn analyzers and establishes a phased strategy for treating warnings as errors. It handles both new projects (immediate enforcement) and legacy codebases (batch-by-batch promotion), ensuring your CI fails on analyzer violations without overwhelming your team. Security rules are always prioritized.
complexity sets up .NET's built-in maintainability analyzers to enforce cyclomatic complexity and coupling limits across your codebase. It configures CA1502, CA1505, and CA1506 rules in .editorconfig and CodeMetricsConfig.txt, then validates thresholds through the build pipeline.
More skills csharpier (MIT) · format (MIT) · resharper-clt (MIT)