analyzer-config
This skill establishes a single source of truth for .NET analyzer severity and code-style rules by creating or normalizing a repo-root .editorconfig file. It detects your current configuration state, structures rule ownership explicitly, and validates that settings are reproducible across local and CI builds.
analyzer-config creates a root .editorconfig to centralize .NET analyzer and style rule configuration for your repository.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-25
analyzer-config creates a root .editorconfig to centralize .NET analyzer and style rule configuration for your repository. This skill establishes a single source of truth for .NET analyzer severity and code-style rules by creating or normalizing a repo-root .editorconfig file. It detects your current configuration state, structures rule ownership explicitly, and validates that settings are reproducible across local and CI builds.
Use it when
- analyzer-config helps you create or normalize a root .editorconfig to centralize .NET analyzer and style rule configuration.
- analyzer-config resolves conflicting or unclear analyzer severity and code-style ownership across a .NET repository by normalizing.
Verify before relying
Read SKILL.md below before installing (5 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/analyzer-config · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does analyzer-config do for .NET projects?
analyzer-config establishes a single source of truth for .NET analyzer severity and code-style rules by creating or normalizing a repo-root .editorconfig file. It detects your current configuration state, structures rule ownership explicitly, and validates that settings are reproducible across local and CI builds.
How do I set up a root editorconfig for a .NET repo?
analyzer-config helps you create or normalize a root .editorconfig to centralize .NET analyzer and style rule configuration. It guides you through structuring rule ownership, detecting conflicts, and establishing a single source of truth for team coding standards across your repository.
How can analyzer-config resolve conflicting analyzer severity?
analyzer-config resolves conflicting or unclear analyzer severity and code-style ownership across a .NET repository by normalizing your .editorconfig structure. It identifies competing rule definitions and consolidates them into a consistent, documented configuration that your entire team can follow.
Can analyzer-config validate rule consistency in CI builds?
Yes. analyzer-config validates that rule severity is reproducible and consistent across local and CI builds. This ensures your analyzer configuration behaves the same way whether developers run it locally or in your continuous integration pipeline.
What if I have no analyzer configuration yet?
analyzer-config can bootstrap analyzer configuration when none is currently structured or documented. It provides guidance on organizing analyzer rules, managing code style rules, and establishing best practices so your repository has a clear, centralized configuration from the start.
Is analyzer-config open source?
Yes, analyzer-config is released under the MIT license, making it free to use, modify, and distribute in both open-source and commercial projects.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
.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
Value
- produce a concrete project delta: code, docs, config, tests, CI, or review artifact
- reduce ambiguity through explicit planning, verification, and final validation skills
- leave reusable project context so future tasks are
(truncated - see the full file via the links below)
File tree — 5 files
catalog/Tools/Analyzer-Config/skills/analyzer-config/SKILL.md
catalog/Tools/Analyzer-Config/skills/analyzer-config/manifest.json
catalog/Tools/Analyzer-Config/skills/analyzer-config/references/analyzer-config.md
catalog/Tools/Analyzer-Config/skills/analyzer-config/references/rules.md
catalog/Tools/Analyzer-Config/skills/analyzer-config/references/template.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Create or normalize a root .editorconfig to centralize .NET analyzer and style rule configuration”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill sets up the .NET SDK's built-in Roslyn analyzers and establishes a phased strategy for treating warnings as errors. It handles both new projects (immediate enforcement) and legacy codebases (batch-by-batch promotion), ensuring your CI fails on analyzer violations without overwhelming your team. Security rules are always prioritized.
cloc delivers line-count, language composition, and branch-diff statistics for .NET codebases through repeatable, configurable commands. Use it to measure solution footprint, compare code deltas across refs, and track codebase composition—not to assess developer productivity or replace design review.
This skill installs and configures Meziantou.Analyzer, a comprehensive rule set for .NET codebases covering design, usage, security, performance, and style concerns. It manages package setup, severity configuration in `.editorconfig`, and avoids duplication with SDK or Roslynator analyzers. Use it when your team wants broader diagnostic coverage without managing multiple analyzer packages.
Roslynator equips .NET projects with open-source static analysis and code-cleanup capabilities through NuGet analyzer packages and an optional command-line tool. Configure rule severity in `.editorconfig`, run analysis and fix workflows, or detect unused code—all while respecting your repo's existing analyzer setup.
stylecop-analyzers sets up the StyleCop.Analyzers package in .NET repositories, establishing clear ownership between root .editorconfig and stylecop.json configuration. It detects existing state, adds the package where needed, and prevents rule overlap with other analyzer packs. Use it when your team requires stronger style conventions than SDK analyzers alone provide.
complexity sets up .NET's built-in maintainability analyzers to enforce cyclomatic complexity and coupling limits across your codebase. It configures CA1502, CA1505, and CA1506 rules in .editorconfig and CodeMetricsConfig.txt, then validates thresholds through the build pipeline.
More skills format (MIT) · resharper-clt (MIT) · modern-csharp (MIT) · csharpier (MIT)