dotnet-editorconfig

Configure .NET code analysis and style rules via .editorconfig and .globalconfig files.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-editorconfig-rudironsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-editorconfig
Source: https://github.com/rudironsoni/dotnet-agent-harness/tree/main/.rulesync/skills/dotnet-editorconfig
Command: npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-editorconfig-rudironsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers precisely control code style, quality, and formatting rules within .NET projects using .editorconfig and .globalconfig files, ensuring consistency and adherence to standards across the codebase.

Core Features & Use Cases

  • Code Style Enforcement: Define preferences for naming, formatting, and modern C# syntax.
  • Code Quality Rule Management: Configure severity (error, warning, suggestion, none) for built-in Roslyn analyzers.
  • Build Integration: Ensure code style rules are enforced during the build process.
  • Use Case: Standardize code formatting across a team by enforcing consistent indentation, naming conventions, and disabling noisy analyzers in test projects.

Quick Start

Configure the dotnet-editorconfig skill to enforce file-scoped namespaces as a warning for all C# files.

Frequently Asked Questions about dotnet-editorconfig

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

FAQPage Schema
How do I configure .NET code analysis rules using .editorconfig files?

Configure .NET code analysis rules by using .editorconfig files to manage IDE and CA diagnostic severities, code style preferences, and Roslyn analyzer settings for C# and Visual Basic projects.

Can I enforce C# code style rules during the build process?

Yes, you can enforce C# code style rules during the build process by configuring build enforcement settings within .editorconfig files to ensure code quality and consistency across your team.

What is the difference between .editorconfig and .globalconfig for .NET projects?

The .editorconfig manages hierarchical code style and analysis rules using file glob patterns, while .globalconfig applies global rule settings across the entire project for consistent developer experience.

How do I set rule severity levels for Roslyn analyzers in C#?

Set Roslyn analyzer severity levels to error, warning, suggestion, or none by configuring the diagnostic severities within your .editorconfig files for granular control over code quality rules.

Does .globalconfig support file glob patterns like .editorconfig?

No, .globalconfig applies global rule settings across the .NET project without file glob patterns, whereas .editorconfig supports hierarchical precedence and granular file glob pattern matching for specific configurations.

How do I disable noisy code analyzers in .NET test projects?

Disable noisy code analyzers in .NET test projects by setting their diagnostic severity to none within an .editorconfig file, utilizing file glob patterns to target specific test project directories.