Flutter Dart Code Review

This is a thorough checklist for reviewing Flutter and Dart code, and it's genuinely library-agnostic, covering BLoC, Riverpod, Provider, GetX, MobX, and Signals with tailored guidance for each. The Dart pitfalls section alone is worth it: it flags implicit dynamics, excessive bang operators, late overuse, and other subtle mistakes that slip through basic linters. The state shape design section nails a common mistake, showing how boolean flags create impossible states and why sealed types or AsyncValue are better. Use this when you want a structured second pass on a Flutter PR or codebase audit. It's opinionated in the right ways, like extracting private build helpers into widgets and avoiding print() in production.

skills.sh installs: 4.7K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill flutter-dart-code-review --agent claude-code

Installs into .claude/skills of the current project.

Files

Flutter/Dart Code Review Best Practices

Comprehensive, library-agnostic checklist for reviewing Flutter/Dart applications. These principles apply regardless of which state management solution, routing library, or DI framework is used.

1. General Project Health

Project follows consistent folder structure (feature-first or layer-first)
Proper separation of concerns: UI, business logic, data layers
No business logic in widgets; widgets are purely presentational
pubspec.yaml is clean — no unused dependencies, versions pinned appropriately
analysis_options.yaml includes a strict lint set with strict analyzer settings enabled
No print() statements in production code — use dart:developer log() or a logging package
Generated files (.g.dart, .freezed.dart, .gr.dart) are up-to-date or in .gitignore
Platform-specific code isolated behind abstractions