code-style-conventions

To enforce consistent dotnet code style, you can apply automated conventions that guide PR reviews and onboarding. This ensures compliance with rules like 120-character line limits and primary constructor usage across all new or refactored code.

You should propagate CancellationToken across async boundaries whenever writing asynchronous .NET code to enable proper task cancellation. Applying standard code conventions ensures this token is correctly threaded through all dependent operations.

The best way to standardize .NET exception handling and logging is to codify conventions requiring dedicated exception types for business errors and English messages for all logs. This improves error tracking and readability.

Yes, you can use primary constructors for dependency injection in C# where appropriate. Establishing a code style convention provides clear guidance on when to apply them, ensuring dependency injection remains consistent and readable across the repository.

Yes, this code style convention skill works with existing refactored code as well as new code. It automates the enforcement of styling rules to speed up reviews, reduce defects, and improve maintainability during repository updates.