dotnet-add-analyzers

Configure .NET analyzers, EditorConfig severities, and compatibility flags.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-add-analyzers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-add-analyzers
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-add-analyzers
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-add-analyzers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers integrate and configure .NET code analyzers to improve code quality, enforce coding standards, and catch potential issues early in the development lifecycle.

Core Features & Use Cases

  • Built-in Roslyn Analyzers: Configure analysis levels for comprehensive rule sets.
  • EditorConfig Severity Overrides: Fine-tune rule severity for specific projects or file types.
  • Nullable Reference Types: Enable and manage nullable context for safer code.
  • Trimming and AOT Compatibility: Ensure applications and libraries are compatible with trimming and Ahead-of-Time compilation.
  • Third-Party Analyzers: Integrate popular external analyzer packages.
  • Use Case: A team wants to enforce stricter coding standards and ensure their .NET library is compatible with Native AOT compilation. They use this Skill to enable all built-in analyzers, configure specific rules via .editorconfig, and set IsTrimmable and IsAotCompatible properties.

Quick Start

Configure the .NET project to use the 'latest-all' analysis level and enforce code style in the build by adding the provided XML to Directory.Build.props.

Frequently Asked Questions about dotnet-add-analyzers

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

FAQPage Schema
How do I configure .NET analyzers to enforce code quality standards?

To configure .NET analyzers, you can set the analysis level to 'latest-all' in your Directory.Build.props and enforce code style rules during the build process. This integrates built-in Roslyn rules and manages project compatibility flags for applications and libraries.

What is the best way to override Roslyn analyzer severity for specific projects?

Overriding Roslyn analyzer severity is done by fine-tuning rule configurations in an EditorConfig file. This allows you to adjust specific rule severities for individual projects or file types without altering the global analysis level.

How do I ensure my .NET library is compatible with Native AOT and trimming?

To ensure .NET library compatibility with Native AOT and trimming, you need to configure trimming and AOT compatibility checks. This involves setting specific project properties like IsTrimmable and IsAotCompatible to validate compatibility.

Can I integrate third-party Roslyn analyzer packages alongside built-in rules?

Yes, you can integrate third-party analyzer packages alongside built-in Roslyn rules. This allows you to combine comprehensive default rule sets with external packages to expand static analysis coverage for your .NET projects.

How do I enable nullable reference types for safer code in a .NET project?

Enabling nullable reference types for safer .NET code involves turning on the nullable context within your project configuration. This activates specific analyzers that detect potential null reference violations during compilation.