flutter-dart-code-review

To review Flutter and Dart code systematically, evaluate changes against a library-agnostic checklist covering widget composition, state management discipline across BLoC/Riverpod/Provider/GetX/MobX/Signals, and separation of concerns to produce a prioritized list of issues and concrete fixes.

A Dart code review checklist targets strict typing pitfalls, null-safety misuse, unsafe exception handling, and inefficient patterns to prevent runtime bugs and maintain code correctness.

Verify Flutter widget rebuild boundaries and disposal by checking const usage, disciplined subscriptions, and disposal behavior in state management layers to ensure UI performance and prevent memory leaks.

Yes, this code review approach is library-agnostic and explicitly verifies state management discipline across BLoC, Riverpod, Provider, GetX, MobX, and Signals to ensure consistent coding standards regardless of the chosen architecture.

The best way to enforce accessibility and security standards is to validate Flutter code changes against a comprehensive checklist that targets specific accessibility concerns, security vulnerabilities, navigation, and error handling.

Yes, you can check dependency injection and internationalization during a PR review by evaluating code changes against a best-practices checklist that targets DI, i18n, and testing coverage expectations.