flutter-dart-code-review

Use a structured checklist covering widget decomposition, const usage, state management architecture, performance, testing, accessibility, and security. This Skill provides 15 review categories with concrete pass/fail criteria applicable to any Flutter project.

Check for implicit dynamic types, excessive null-assertion operators, broad catch clauses, unused async modifiers, late overuse, and missing Dart 3 pattern matching. Also verify strict analyzer settings like strict-casts and strict-inference in analysis_options.yaml.

Yes, the state management section is library-agnostic and includes a mapping table translating universal principles to BLoC, Riverpod, Provider, GetX, MobX, Signals, and built-in setState. Solution-specific conventions like Riverpod's ref.watch chains are addressed individually.

Use sealed classes, union variants, or AsyncValue instead of boolean flags like isLoading and hasError, which allow impossible state combinations. Every async operation should model loading, success, and error as distinct exhaustive states.

Using BuildContext after an await without checking context.mounted can reference a disposed widget, causing crashes. Always verify the widget is still mounted before navigation, dialogs, or setState in async callbacks, and never store BuildContext in singletons.

A checklist identifies known anti-patterns but cannot execute the app, measure actual runtime performance, or verify visual output. Combine it with flutter analyze in CI, widget tests, and profiling tools for complete coverage.