dotnet-code-review

Review .NET code changes for bugs, regressions, and missing tests.

466|35|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-code-review
Source: https://github.com/managedcode/dotnet-skills/tree/main/skills/dotnet-code-review
Command: npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure .NET code changes are robust, secure, and maintainable by providing a structured review process before merging.

Core Features & Use Cases

  • Comprehensive Checklist: Covers correctness, concurrency, security, and more.
  • Pattern Guidance: Offers best practices for async, disposal, and security.
  • Use Case: When reviewing a pull request for a new API endpoint, use this Skill to systematically check for potential bugs, security vulnerabilities, and adherence to .NET best practices.

Quick Start

Review the attached .NET code changes using the dotnet-code-review skill.

Frequently Asked Questions about dotnet-code-review

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

FAQPage Schema
How do I review .NET code changes for bugs and security vulnerabilities?

To review .NET code changes, apply a structured checklist covering correctness, concurrency, data integrity, and security. This process identifies bugs, architectural drift, and platform-specific pitfalls before merging.

What are the best practices for async and disposal behavior in .NET code reviews?

Best practices for async and disposal behavior involve referencing detailed checklists and common patterns to ensure correct resource lifecycle management, concurrency safety, and proper disposal during your .NET code review.

How do I check .NET pull requests for architectural drift and missing tests?

Checking .NET pull requests for architectural drift and missing tests requires systematically reviewing application code, libraries, and tooling against established patterns to ensure maintainability and robustness.

Does this code review process work for .NET libraries and infrastructure changes?

Yes, this code review process applies to .NET libraries, tests, tooling, and infrastructure changes, systematically evaluating them for security compliance, disposal behavior, and platform-specific pitfalls.

How do I ensure concurrency safety and resource lifecycle management in .NET?

Ensuring concurrency safety and resource lifecycle management involves reviewing .NET code changes for incorrect async behavior and disposal patterns, verifying data integrity and security compliance through established checklists.