Contributing to Roslynator

Guidelines for contributing to the Roslynator repo.

Agent Skills

Global agent rules: AGENTS.md.

Agent skills in .claude/skills/ are step-by-step workflows for AI coding agents (Cursor, Claude Code). They also work as readable contributor guides — open any SKILL.md in that folder.

Skill	Use when
add-analyzer	New RCS#### analyzer
add-refactoring	New RR#### refactoring
add-compiler-diagnostic-fix	New CS#### / RCF#### fix
fix-analyzer-bug	False positive, false negative, or bad transformation
deprecate-analyzer-or-refactoring	Obsolete or retire a rule
release-roslynator	Release preparation (maintainers)

More context: Contributing with agent skills on the docs site.

Submitting Pull Requests

• DO submit issues for bug fixes or features.
• DO add unit tests for bug fixes or features.
• DO ensure submissions pass build and are merge conflict free.
• DO update changelog.
• DO NOT submit new analyzer/refactoring/fix without discussing it first.
• DO NOT submit large formatting/documentation changes without discussing it first.

Creating Issues

• DO create a new issue rather than commenting on a closed issue.
• DO include the analyzer, refactoring, or error ID in the title (for example, RCSxxxx, RRxxxx, or CSxxxx).
• DO use a descriptive title that identifies the issue or requested feature.
• DO specify a detailed description of the issue or requested feature.
• DO provide the following for bug reports:
  • Describe the expected behavior and the actual behavior.
  • Provide example code that reproduces the issue.
  • Provide any relevant exception messages and stack traces.

Coding Style

• DO follow .NET Runtime Coding Style (except using s_ and t_ prefix for field names).
• DO install the Roslynator extension for Visual Studio or VS Code and follow its suggestions.