菜单
Use when adding a new RCS#### diagnostic in roslynator (RCS0 formatting, RCS1 general, RCS9 code-analysis), wiring roslynator_* EditorConfig options, or when docs say CHANGELOG.md, XunitDiagnosticVerifier, or analyzers-testing.md — those are wrong for in-repo contribution.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dotnet/roslynator --skill add-analyzer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v* release, or optionally tagging cli-v*.
Use when adding a Roslynator code fix for C# compiler error CS#### or RCF####, editing Diagnostics.xml or CodeFixes.xml, or when compiler-diagnostic-fixes-testing.md shows XunitCompilerDiagnosticFixVerifier or bare DiagnosticId like "CS0106" — in-repo uses AbstractCSharpCompilerDiagnosticFixVerifier and CompilerDiagnosticIdentifiers. Contributor how-to exists but testing page targets NuGet consumers.
Use when adding a new RR#### refactoring in roslynator, editing Refactorings.xml, registering in RefactoringContext, or when refactorings-testing.md shows XunitRefactoringVerifier — in-repo uses AbstractCSharpRefactoringVerifier and CHANGELOG.md.
基于 SOC 职业分类
正在显示 SKILL.md
| name | add-analyzer |
| description | Use when adding a new RCS#### diagnostic in roslynator (RCS0 formatting, RCS1 general, RCS9 code-analysis), wiring roslynator_* EditorConfig options, or when docs say CHANGELOG.md, XunitDiagnosticVerifier, or analyzers-testing.md — those are wrong for in-repo contribution. |
Roslynator analyzers are metadata-driven: edit Analyzers.xml, codegen, implement analyzer + code fix, test, changelog. New analyzers never set <Status> — only IsEnabledByDefault.
RCS0 / RCS1 / RCS9 rule requested in an approved issueroslynator_* config optionRCS0 → Formatting, RCS1 → Analyzers, RCS9 → CodeAnalysis.AnalyzersNot for: deprecating rules (deprecate-analyzer-or-refactoring), bug fixes (fix-analyzer-bug), refactorings (add-refactoring).
Gate: CONTRIBUTING.md requires an approved GitHub issue before implementation.
Read this skill and references/implementation.md before writing tests. Published analyzers-testing.md targets NuGet consumers — copying it produces code that does not compile in this repo.
STOP. Do NOT edit Analyzers.xml, run codegen, or implement until the user has confirmed every required parameter below. Do not invent defaults when the user (or issue) did not state them.
Use AskQuestion when available; otherwise ask conversationally. Batch related choices.
| Parameter | Required? | Allowed / notes |
|---|---|---|
Id | propose | Compute next free RCS0 / RCS1 / RCS9 id from Analyzers.xml; do not ask unless the issue conflicts or multiple ids are plausible |
Identifier | yes | PascalCase; drives generated names |
Title | yes | Short description |
DefaultSeverity | yes | Hidden, Info, Warning, or Error — always ask |
IsEnabledByDefault | yes | true / false — always ask (RCS0 often false) |
MessageFormat | if message has {n} placeholders | Otherwise omit (same as Title) |
| Code fix? | yes | Strongly recommended; confirm yes/no |
SupportsFadeOut / fade-out analyzer | no | Ask only if unused-code style |
MinLanguageVersion | no | Ask only if C# version-gated |
| Config option | no | See config-options.md |
When proposing Id, state the chosen value in your plan/summary (e.g. “using next free RCS9012”). Skip asking other parameters only when the approved issue or the user's message already states the value explicitly.
| Step | Location / command |
|---|---|
| Metadata | src/Analyzers.xml — see analyzer-schema.md |
| Config option | src/ConfigOptions.xml — see config-options.md |
| Codegen | cd tools && pwsh ./generate_code.ps1 |
| Analyzer | RCS1 → Analyzers/CSharp/Analysis/; RCS0 → Formatting.Analyzers/CSharp/; RCS9 → CodeAnalysis.Analyzers/CSharp/ |
| Code fix | matching *.CodeFixes/CSharp/CodeFixes/ |
| Tests | src/Tests/<Package>.Tests/RCS####IdentifierTests.cs |
| Changelog | CHANGELOG.md under ## [Unreleased] |
<Analyzer> entry; schema in references/analyzer-schema.md. Use docs-site analyzer-metadata, not Template.Analyzers.xml.tools/ (required cwd — see Common Mistakes).Changelog line:
- Add analyzer "TITLE" ([RCS1234](https://josefpihrt.github.io/docs/roslynator/analyzers/RCS1234)) ([#PR](https://github.com/dotnet/roslynator/pull/PR))
Verify:
cd tools && pwsh ./generate_code.ps1
cd src && dotnet build Roslynator.sln
cd src && dotnet test Roslynator.sln --no-build --filter "FullyQualifiedName~RCS####"
cd src && dotnet format Roslynator.sln --no-restore --verify-no-changes --severity info
| Mistake | Fix |
|---|---|
Guess DefaultSeverity / IsEnabledByDefault | Ask — hard gate above |
Follow analyzers-testing.md verbatim | In-repo: AbstractCSharpDiagnosticVerifier + Descriptor = DiagnosticRules.X |
pwsh tools/generate_code.ps1 from repo root | Run cd tools && pwsh ./generate_code.ps1 — generator uses ../src relative to cwd |
<Status> on new analyzer | Use only IsEnabledByDefault; lifecycle is deprecate-analyzer-or-refactoring |
context.ReportDiagnostic | Use DiagnosticHelpers.ReportDiagnostic |
Lazy SupportedDiagnostics field initializer | Use Immutable.InterlockedInitialize pattern |