rm-guide-code-quality

Enforce null-safety and readability in C# code reviews by applying guardrails that require `is null` checks, prefer records for immutable DTOs, and keep expression-bodied members small and focused to avoid confusing constructs.

The best way to review immutable DTOs in .NET service code is to advocate for using C# records, which enforce immutability, alongside precise XML documentation to enhance API discoverability and maintainability.

Use `is null` and `is not null` checks for C# public APIs to reduce bugs and enforce consistent null handling, replacing clever or confusing equality operator constructs with clear pattern matching.

Evaluate expression-bodied members for maintainability during a C# review by ensuring methods remain small and focused, applying restrained usage of expression-bodied syntax to prioritize clarity over concise but confusing constructs.

This C# readability guide encourages adding XML docs to public APIs when they enhance discoverability, maintaining precision in documentation rather than mandating it universally across all evaluated methods.