dotnet-code-review

To review .NET pull requests for async and disposal issues, apply a structured checklist evaluating async flows, resource disposal, and concurrency to generate concrete, file-referenced findings before merging.

A .NET code review should catch concurrency regressions, incorrect disposal behavior, security vulnerabilities, inefficient EF queries, middleware order issues, and missing test coverage to ensure changes are shippable.

To check Entity Framework queries for performance risks in a .NET PR, evaluate data access patterns against best practices using structured reference materials to identify and report design issues with file-referenced findings.

Yes, you can use a structured checklist to verify .NET middleware order and security by systematically applying best practice patterns to your changes and enforcing correctness before merge.

To ensure .NET code changes have adequate testing coverage before merging, enforce best practices through a structured review workflow that evaluates testing coverage and reports missing tests with concrete file references.