review-code

Perform a structured C# .NET code review by applying priority-based checklists across code quality, security, testing, performance, and documentation. Use standardized templates for inline comments and generate a formal review summary to capture findings and next steps.

During a .NET code audit, evaluate domain logic, repository patterns, and API endpoints against priority-based checklists. Enforce .editorconfig compliance to ensure alignment with Clean Architecture and best practices across application and infrastructure layers.

Yes, you can standardize code review feedback using CRITICAL, IMPORTANT, and SUGGESTION templates. These templates help format inline comments consistently, making the review process more structured and actionable for C#/.NET projects.

Yes, the code review process explicitly enforces .editorconfig compliance for dotnet projects. It checks code against .editorconfig rules alongside priority-based checklists covering security, performance, and documentation to ensure comprehensive evaluation.

The best way to document C# code review findings is to generate a structured Review Summary. This formal output captures all findings from the priority-based checklists and outlines actionable next steps for the development team.

Automated checklists for .NET code reviews focus on structured, repeatable evaluation across specific domains like security and performance. They do not replace human judgment for complex architectural assessments but provide a consistent baseline for identifying issues.