.NET Analyzer Configuration

Trigger On

• the repo needs a root .editorconfig
• analyzer severity and style ownership are unclear
• the team wants one source of truth for rule configuration

Workflow

1. Prefer one repo-root .editorconfig with root = true.
2. Add nested .editorconfig files when a subtree has a clear scoped purpose, such as stricter rules, different generated-code handling, or a different policy for tests or legacy code.
3. Keep severity in .editorconfig, not scattered through IDE settings.
4. Write the file as real EditorConfig, not as a made-up .NET variant:

- lowercase filename .editorconfig - root = true in the preamble - no inline comments - forward slashes in globs

1. Keep bulk switches such as EnableNETAnalyzers in MSBuild files, not in .editorconfig.
2. Treat .globalconfig as an exceptional case, not the normal repo setup.

Deliver

• one explicit analyzer configuration ownership model
• a root .editorconfig layout that agents can extend safely

Validate

• rule severity is reproducible in local and CI builds
• IDE-only settings do not silently override repo policy
• the default path is a root .editorconfig, not a surprise alternative

Load References

Related skills

Related agents