C# Code Review Checklist for Pull Requests (video)

A concise C# code review checklist covering exceptions, async, testing, complexity, security, and logging — plus when to add automated scanning.

Read the full article

Transcript

C# Code Review Checklist for Pull Requests. Here's the short version.

Use this checklist during C# pull request review. Not every item applies to every change — focus on sections relevant to the files touched.

Correctness and behavior. Does the change match the stated requirement or ticket? Are edge cases handled (null inputs, empty collections, boundary values)? Do unit or integration tests cover new behavior and regressions?

Exceptions and logging. No empty catch blocks unless explicitly documented. Exceptions logged with correlation or request context where available. No silent swallowing of failures in background or payment flows.

Async and performance. Async methods use await rather than blocking calls. Database and HTTP calls are not accidentally synchronous in hot paths. Large allocations or N+1 query patterns flagged in data access code.

Want to find these issues in your own code? Connect your GitHub repository to CodeInspector. You'll get findings with the file, line, severity, and a recommended fix, plus HTML and PDF reports for your team. Start free at codeinspector.app.

More videos

All videos