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
Install
managedcode/dotnet-skills/analyzer-config · repository language: C#
git clone https://github.com/managedcode/dotnet-skills
cp -r dotnet-skills/catalog/Tools/Analyzer-Config/skills/analyzer-config ~/.claude/skills/analyzer-confignpx skillfed install managedcode/dotnet-skills/analyzer-configFrequently 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)
Read as markdown · JSON record · Browse the source repository
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