analyzers

Creates Roslyn analyzers for EF Core to enforce coding standards and catch issues at compile time.

14.8k|3.4k|Updated Jan 23, 2014
One-click install
npx skills add https://github.com/dotnet/efcore --skill analyzers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzers
Source: https://github.com/dotnet/efcore/tree/main/.agents/skills/analyzers
Command: npx skills add https://github.com/dotnet/efcore --skill analyzers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing and maintaining Roslyn analyzers for EF Core to enforce coding standards and catch issues during development.

Core Features & Use Cases

  • Templates and guidance for building EF Core-specific Roslyn analyzers
  • Support for validating code against EF Core provider changes and diagnostics
  • Use Case: When adding new EF Core features or diagnosing performance issues, create or update analyzers to enforce correct usage patterns

Quick Start

Create a new Roslyn analyzer project for EF Core, scaffold a sample rule, and wire it into your solution to begin validation.

Frequently Asked Questions about analyzers

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

FAQPage Schema
How do I create Roslyn analyzers for EF Core to catch compile-time issues?

You can create Roslyn analyzers for EF Core by scaffolding a new analyzer project, implementing diagnostic rules, and wiring them into your solution to validate code against EF Core provider changes during development.

What are EF Core Roslyn analyzers and when do I need them?

EF Core Roslyn analyzers are diagnostic rules that enforce correct usage patterns and catch issues at compile time. You need them when adding new EF Core features or diagnosing performance issues to maintain code quality.

How do I scaffold a sample diagnostic rule for an EF Core analyzer?

To scaffold a sample diagnostic rule, create a new Roslyn analyzer project for EF Core, use the provided templates to generate the rule structure, and wire it into your solution to begin validation.

Does this approach support validating code against EF Core provider changes?

Yes, the EF Core Roslyn analyzer templates support validating code against provider changes and diagnostics, allowing you to enforce coding standards and catch compatibility issues during development.

What's the best way to maintain existing EF Core diagnostic rules?

The best way to maintain EF Core diagnostic rules is to update existing analyzers when adding new features or diagnosing performance issues, ensuring they continue to enforce correct usage patterns and catch issues at compile time.

Do I need a specific project structure to develop EF Core analyzers?

You need a Roslyn analyzer project with frontmatter metadata including name and description, support for optional resource directories, and wiring into your solution to validate EF Core code.