flutter-dart-code-review

Use a structured checklist covering widget decomposition, const usage, state management discipline, performance, and security. This Skill provides category-by-category review items so reviewers can systematically flag issues like business logic in widgets or missing disposal.

Common pitfalls include implicit dynamic types, excessive null-assertion operators, catching Error subtypes, unused async markers, and print() in production code. Enabling strict-casts, strict-inference, and strict-raw-types in analysis_options.yaml catches many of these automatically.

Yes, the checklist is library-agnostic and includes a quick-reference table mapping universal principles to BLoC, Riverpod, Provider, GetX, MobX, Signals, and setState. It flags solution-specific issues like bloc-to-bloc dependencies or missing autoDispose.

Use const constructors, scope state consumers narrowly, apply selectors to rebuild only on relevant field changes, and avoid expensive work in build(). RepaintBoundary and AnimatedBuilder child parameters further isolate repaints.

Avoid boolean flags like isLoading and hasError when states are mutually exclusive, since they allow impossible combinations. Use sealed classes, union variants, or AsyncValue so loading, success, and error states are exhaustive and unrepresentable when invalid.