skills.rest
Postpartum-genushyacinthus29
Postpartum-genushyacinthus29COMMUNITY
Explore all skills by this author →
GitHub

dotnet-analyzer-config

Configure a central .editorconfig to standardize .NET analyzer and style rules.

8|Updated Mar 29, 2026
Search Tags:#dotnet#code-analysis#editorconfig#repository-config#style-rules#rule-ownership
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-analyzer-config-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-analyzer-config
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-analyzer-config
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-analyzer-config-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensure consistent .NET analyzer and style rule application across a repository by centralizing configuration in a repo-root .editorconfig.

Core Features & Use Cases

  • One repo-root .editorconfig with root = true as single source of truth
  • Nested .editorconfig files for subtree-scoped overrides
  • Bootstrap, verify, and maintain rule ownership to reduce ambiguity

Quick Start

Run the Ralph Loop to plan, bootstrap, and validate a root .editorconfig and any subtree overrides.

Frequently Asked Questions about dotnet-analyzer-config

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

FAQPage Schema
How do I enforce .NET analyzer rules across an entire repository?▼

To enforce .NET analyzer rules repo-wide, configure a central root .editorconfig file with `root = true` to serve as the single source of truth for style rules and analyzer configurations.

Can I use nested .editorconfig files for subtree-scoped overrides in .NET?▼

Yes, you can use nested .editorconfig files within your repository to apply subtree-scoped overrides, clarifying rule ownership and consistency for specific project directories.

What is the best way to centralize .NET style rules and reduce ambiguity?▼

The best way to centralize .NET style rules is bootstrapping a single repo-root .editorconfig, which clarifies rule ownership and reduces configuration ambiguity across all projects.

Does a root .editorconfig work with existing .NET analyzers in my projects?▼

Yes, a root .editorconfig works with .NET analyzers by standardizing and enforcing style rules across projects where a single root configuration and subtree overrides are desired.

How do I bootstrap and validate rule ownership for .NET code analysis?▼

Bootstrap and validate .NET code analysis rule ownership by running a planning loop to create a root .editorconfig, add nested overrides, and verify configuration consistency.

Related Skills

Explore More Software Engineering Skills→
managedcodemanagedcode
466

dotnet-analyzer-config

Create a repository-wide .editorconfig file configuring .NET analyzer and style rules.

Official
Intermediate
dodygdodyg

dotnet-editorconfig

Generate .editorconfig files to enforce .NET code style and analysis rules.

Community
Intermediate
Postpartum-genushyacinthus29Postpartum-genushyacinthus29
8

dotnet-format

Apply dotnet format to fix or verify code style in .NET repositories.

Community
Intermediate
managedcodemanagedcode
466

dotnet-format

Apply code formatting and analyzer fixes to .NET projects via dotnet format.

Official
Intermediate