roslyn-analyzers

Design, validate, and ship Roslyn analyzers for netstandard2.0 projects.

9|1|Updated Jun 6, 2025

Search Tags:#csharp #linting #code-quality #static-analysis #roslyn #diagnostic #analyzers

Ready to run

npx skills add https://github.com/JeremyKuhne/touki --skill roslyn-analyzers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: roslyn-analyzers
Source: https://github.com/JeremyKuhne/touki/tree/main/.agents/skills/roslyn-analyzers
Command: npx skills add https://github.com/JeremyKuhne/touki --skill roslyn-analyzers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Roslyn analyzers skill helps teams design, validate, and ship custom Roslyn analyzers, avoiding duplication by first surveying existing analyzers, and guiding the workflow from design through release.

Core Features & Use Cases

Guidance on stateless analyzer design, registration patterns, and performance practices for Roslyn analyzers.
Step-by-step workflow from design to validation, tests, and packaging inside Touki.

Quick Start

Identify an unmet rule in your codebase and implement a Roslyn analyzer following the project’s design guidelines.

Frequently Asked Questions about roslyn-analyzers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a stateless Roslyn analyzer for C# code quality analysis?▼

Design stateless Roslyn analyzers by using compilation-start actions and narrow syntax registrations to ensure thread safety. This approach enforces C# coding standards efficiently without duplicating existing analyzer rules in your static analysis workflow.

What is the workflow for building and shipping custom Roslyn analyzers?▼

The workflow for building custom Roslyn analyzers involves surveying existing rules, designing the analyzer, validating it, writing tests, and packaging. This ensures your code quality diagnostic tools meet performance guidelines before release.

Can I include code fixes when creating Roslyn analyzers for netstandard2.0 projects?▼

Yes, you can include optional code fixes when developing Roslyn analyzers for netstandard2.0 projects. This allows your static analysis diagnostics to automatically provide corrective actions for identified C# code quality violations.

How do I track custom diagnostic rules in Roslyn analyzer releases?▼

Track custom diagnostic rules in Roslyn analyzer releases by maintaining an AnalyzerReleases file. This practice ensures your C# static analysis rules are documented and versioned correctly across your team's code quality enforcement lifecycle.

Why should I survey existing Roslyn analyzers before implementing new ones?▼

Survey existing Roslyn analyzers before implementation to avoid duplicating established C# static analysis rules. Checking current diagnostic offerings prevents redundant code quality checks and maintains consistent linting standards across projects.