Flutter/Dart Code Review
Library-agnostic Flutter review checklist for Muse: widgets, state management (BLoC, Riverpod, GetX, MobX), Dart pitfalls, performance, testing, and security.
- What
- Library-agnostic Flutter review checklist for Muse: widgets, state management (BLoC, Riverpod, GetX, MobX), Dart pitfalls, performance, testing, and security.
- Cost
- Free
- Needs
- none to install. Pure guidance; have the Flutter/Dart code or PR to review ready, and know which state management the project uses.
- Level
- Beginner
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a comprehensive, library-agnostic code review checklist for Flutter and Dart that works whatever state management the project uses. Fifteen review areas: project health (folder structure, separation of concerns, clean pubspec, strict analysis_options), Dart language pitfalls (implicit dynamic, null safety misuse, catching Error, late overuse, print in production, missing Dart 3 pattern matching), widget best practices (decomposition under 80 to 100 line build methods, const constructors, key usage, theming from colorScheme not hardcoded colors, no work in build()), state management principles that adapt to BLoC, Riverpod, Provider, GetX, MobX, and Signals (business logic out of widgets, immutable state with copyWith or proper reactive mutation, sealed types instead of boolean flag soup, narrow rebuild scopes, disposal hygiene, mounted checks after async gaps), performance (const to stop rebuilds, no expensive work in build, image caching, ListView.builder, deferred loading), testing (unit, widget, integration, golden tests, 80%+ on business logic), accessibility (semantics, contrast, 48px targets, no color-only state), platform concerns (iOS/Android differences, responsive layouts), security (secure storage, no hardcoded API keys, input validation, HTTPS), package review (pub points, verified publishers, version constraints), navigation and routing, error handling (FlutterError.onError, Crashlytics/Sentry, graceful degradation), internationalization, dependency injection, and static analysis enforcement. Includes a quick-reference table mapping each principle to its implementation per state management solution. Use when reviewing Flutter or Dart code, regardless of the libraries involved. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: a checklist, not a substitute for running the app on real devices; opinions on state management are deliberately neutral, your team's chosen solution still needs its own depth; 15 areas is a lot, prioritize by risk. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Flutter/Dart Code Review is a free Muse skill and comprehensive, library-agnostic code review checklist for Flutter and Dart that works whatever state management the project uses. Its fifteen review areas cover project health, folder structure, separation of concerns, clean pubspec, Dart pitfalls like implicit dynamic and null safety misuse, plus widgets, state management, performance, testing and security.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Flutter/Dart Code Review" with your Muse. Prerequisites: none to install. Pure guidance; have the Flutter/Dart code or PR to review ready, and know which state management the project uses. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/flutter-dart-code-review/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review this Flutter code: [paste code or describe the PR]. State management: [BLoC/Riverpod/GetX/...]." 3. Ask it to adapt the state management section to your solution and to prioritize findings by risk. Tip: ask for the top 5 issues only on a first pass over a large PR. Safety: a skill is plain-text instructions; it runs nothing by itself. Review before merging; run on device, not just in review.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.