review-dotnet

Identify language and runtime conformance issues in C# and F# code.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-dotnet
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/review-dotnet
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing .NET source code to enforce consistent language and runtime conventions (async/await, nullable references, IDisposable patterns, LINQ usage, API stability, and testability) helps teams catch quality issues early and improve maintainability without performing security or architectural reviews.

Core Features & Use Cases

  • Analyze C# and F# code for recommended async/await usage and proper ConfigureAwait usage.
  • Detect nullable reference type usage and NRE avoidance patterns across code paths.
  • Review public API surface stability and versioning signals in libraries and packages.
  • Validate resource management with IDisposable / IAsyncDisposable and using patterns.
  • Inspect collections and LINQ usage for efficiency and safety (avoidance of multiple enumeration, memory impact).
  • Assess testability considerations (DI, sealed vs. overridable, static usage) where applicable.

Quick Start

Provide a code scope (files or diffs) containing .NET code, and I will return a findings list of language-dotnet results.

Frequently Asked Questions about review-dotnet

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

FAQPage Schema
How do I review C# code for async/await and nullable reference issues?

To review C# code for async/await and nullable reference issues, provide your source files or diffs for analysis. The tool identifies language-runtime findings, focusing on ConfigureAwait usage, NRE avoidance patterns, and returning categorized results with file locations and suggestions.

What is the best way to check IDisposable usage and LINQ patterns in .NET?

Checking IDisposable usage and LINQ patterns in .NET involves analyzing your code scope for multiple enumeration risks and proper using statements. The review process validates resource management with IAsyncDisposable and inspects collection efficiency, outputting severity-tagged findings.

Can I analyze F# source code for runtime conformance and testability?

Yes, you can analyze F# source code for runtime conformance and testability. The review evaluates F# sources within a project or diff, assessing dependency injection, static usage, and overridable structures, then reports findings categorized under language-dotnet.

How do I validate public API surface stability in a .NET library?

Validating public API surface stability in a .NET library requires providing the library's code scope for review. The analysis detects versioning signals and API stability issues across your public surface, generating a detailed findings list with locations, titles, and optional suggestions.

Does this .NET code review cover security vulnerabilities or architectural design?

No, this .NET code review does not cover security vulnerabilities or architectural design. It strictly focuses on language and runtime conformance, including async/await, nullable references, IDisposable patterns, LINQ efficiency, and testability to improve maintainability.

What format do the code review findings follow for .NET projects?

The code review findings for .NET projects follow a structured format including file and line location, category language-dotnet, severity, title, and description. Findings also include an optional suggestion to guide fixes for identified runtime convention issues.