mcaf-dotnet-analyzer-config

Configure .NET analyzer and style rules via a root .editorconfig file.

4|Updated Mar 6, 2026

Search Tags:#code style #configuration #.net #analyzer #editorconfig #.net sdk

Ready to run

npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-analyzer-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcaf-dotnet-analyzer-config
Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-dotnet-analyzer-config
Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-dotnet-analyzer-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing and standardizing .NET code analysis rules across a repository, ensuring consistency and clarity in code quality and style.

Core Features & Use Cases

Centralized Configuration: Establishes a single source of truth for .NET analyzer severities and style options using .editorconfig.
Rule Clarity: Makes analyzer ownership and rule configurations explicit, reducing ambiguity.
Use Case: When a .NET project has inconsistent code style violations or unclear analyzer rule severities, this Skill can generate a comprehensive root .editorconfig file to enforce desired standards.

Quick Start

Use the mcaf-dotnet-analyzer-config skill to create a root .editorconfig file for this .NET repository.

Frequently Asked Questions about mcaf-dotnet-analyzer-config

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

FAQPage Schema

How do I configure .NET analyzer rules for code style and severity?▼

You configure .NET analyzer rules by generating a repository-root .editorconfig file that establishes a single source of truth for analyzer severities, code-style options, and section layout. This ensures consistent code quality standards across the entire repository.

What is the best way to enforce consistent code style across a .NET repository?▼

The best way to enforce consistent code style is to use a centralized .editorconfig file to make analyzer ownership and rule configurations explicit. This approach reduces ambiguity and standardizes code analysis rules throughout your .NET project.

Can I use nested .editorconfig files for subtree-specific .NET analyzer rules?▼

Yes, you can use nested .editorconfig files to apply subtree-specific configurations within your .NET repository. This allows different directories to have tailored analyzer rules while respecting the root configuration and AGENTS.md commands.

How do I fix inconsistent code style violations in a .NET project?▼

To fix inconsistent code style violations, generate a comprehensive root .editorconfig file that explicitly defines desired analyzer rule severities and style options. This establishes clear standards and eliminates ambiguity in code quality enforcement.

Does the .NET SDK support .editorconfig for analyzer configuration?▼

Yes, the .NET SDK supports .editorconfig files for configuring analyzer rules and code style options. You can establish rule severity, define style preferences, and structure section layout directly within this configuration file.

When do I need an .editorconfig file for .NET code analysis?▼

You need an .editorconfig file when your .NET repository requires explicit rule severity definitions, standardized code-style options, clear analyzer ownership, or structured section layout to maintain consistent code quality and style across the project.